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

Root ICS/CM9-JB/CM10 Development Thread

I'm having issues receiving MMS, and when trying to send MMS the messaging app force closes on LG855 on Boost Mobile.

Get a logcat for the fc. I will try to dig up the proper mms settings for boost for the next build.
 
Loaded test 5 aokp on a very clean boot: (wipe clean + format sd card)

menu and search icons are flashing, the other two are off (after a while they all stayed off)
phone works
- haven't tried bluetooth
- if i have a headset plugged in and I enable speakerphone, it doesn't work, but it fixes itself when i unplug the headset so this is a low priority problem
3g came up fine, data works
browser keeps crashing
voice search doesn't work (doesn't register speech)

downloaded jb google apps from xda (2012-07-26 for jb 4.1.1) and installed from recovery

google apps work great. market, maps, gmail, etc.
camera app is behaving strange. dark screen, controls don't respond. had to hit home to exit. same with camera zoom fx, so this is probably a problem with an API call not returning...
contacts sync took forever. calendar was a little faster, but both much slower than usual. (those are the only things i sync)
sms works (receiving and sending). didn't try mms
trying to play a youtube video from a link in gmail froze the phone
- screen was frozen and didn't respond to touches
- after a while the screen went black and it woke back up again when i hit power
- hitting home didn't do anything
- had to pull battery
- how do i get some useful log out to you?
GPS works, sees several satellites and narrows down to ~100 feet reasonably quickly (inside, overcast, without wifi assistance)

overall, this is a very functional ROM, maybe even a daily driver! thanks so much!

note: i am on sprint
 
  • Like
Reactions: tdm
Get a logcat for the fc. I will try to dig up the proper mms settings for boost for the next build.

[HIGH]E/WorkingMessage( 2245): WorkingMessage.send MMS sending failure. mms_config.xml is missing uaProfUrl setting. uaProfUrl is required for MMS service, but can be absent for SMS.
E/WorkingMessage( 2245): java.lang.NullPointerException: WorkingMessage.send MMS sending failure. mms_config.xml is missing uaProfUrl setting. uaProfUrl is required for MMS service, but can be absent for SMS.
E/WorkingMessage( 2245): at com.android.mms.data.WorkingMessage.send(WorkingMessage.java:1170)
E/WorkingMessage( 2245): at com.android.mms.ui.ComposeMessageActivity.sendMessage(ComposeMessageActivity.java:3621)
E/WorkingMessage( 2245): at com.android.mms.ui.ComposeMessageActivity.confirmSendMessageIfNeeded(ComposeMessageActivity.java:683)
E/WorkingMessage( 2245): at com.android.mms.ui.ComposeMessageActivity.onClick(ComposeMessageActivity.java:3269)
E/WorkingMessage( 2245): at android.view.View.performClick(View.java:4084)
E/WorkingMessage( 2245): at android.view.View$PerformClick.run(View.java:16966)
E/WorkingMessage( 2245): at android.os.Handler.handleCallback(Handler.java:615)
E/WorkingMessage( 2245): at android.os.Handler.dispatchMessage(Handler.java:92)
E/WorkingMessage( 2245): at android.os.Looper.loop(Looper.java:137)
E/WorkingMessage( 2245): at android.app.ActivityThread.main(ActivityThread.java:4899)
E/WorkingMessage( 2245): at java.lang.reflect.Method.invokeNative(Native Method)
E/WorkingMessage( 2245): at java.lang.reflect.Method.invoke(Method.java:511)
E/WorkingMessage( 2245): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/WorkingMessage( 2245): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/WorkingMessage( 2245): at dalvik.system.NativeStart.main(Native Method)[/HIGH]

Here's the logcat. I looked back through the thread a bit and couldn't find exactly what fixed the mms stuff before. I might pick through Blood's MIUI stuff and see what he did to make it work there.
 
  • Like
Reactions: tdm
Found a show stopper bug. I can make one phone call. Trying a second phone call causes the phone app to get stuck before actuall dialing. I did not try receiving a phone call. I did install Google Voice before trying my second phone call, but I uninstalled it, rebooted, and still was able to make only one phone call.

I also noticed that while I was talking on the phone, clicking around caused a noticable clicking sound. Minor problem.

Great progress. I'm looking forward to this ROM being fully functional. I bought a SGS3, and this ROM is giving it a run for its money!
 
  • Like
Reactions: tdm
Tdm, I really appreciate the time and effort you are putting into this build and not giving up on it when the times get tough. It says a lot about who you are, bro. Thanks :thumbup:
 
  • Like
Reactions: tdm
Tdm, I really appreciate the time and effort you are putting into this build and not giving up on it when the times get tough. It says a lot about who you are, bro. Thanks :thumbup:

Tdm is the shizznik

P.s.: honarble mentions to bloodawn, monster, ndno, and imfm for getting the balk rolling :beer:
 
  • Like
Reactions: tdm
[HIGH]E/WorkingMessage( 2245): WorkingMessage.send MMS sending failure. mms_config.xml is missing uaProfUrl setting. uaProfUrl is required for MMS service, but can be absent for SMS.
E/WorkingMessage( 2245): java.lang.NullPointerException: WorkingMessage.send MMS sending failure. mms_config.xml is missing uaProfUrl setting. uaProfUrl is required for MMS service, but can be absent for SMS.
E/WorkingMessage( 2245): at com.android.mms.data.WorkingMessage.send(WorkingMessage.java:1170)
E/WorkingMessage( 2245): at com.android.mms.ui.ComposeMessageActivity.sendMessage(ComposeMessageActivity.java:3621)
E/WorkingMessage( 2245): at com.android.mms.ui.ComposeMessageActivity.confirmSendMessageIfNeeded(ComposeMessageActivity.java:683)
E/WorkingMessage( 2245): at com.android.mms.ui.ComposeMessageActivity.onClick(ComposeMessageActivity.java:3269)
E/WorkingMessage( 2245): at android.view.View.performClick(View.java:4084)
E/WorkingMessage( 2245): at android.view.View$PerformClick.run(View.java:16966)
E/WorkingMessage( 2245): at android.os.Handler.handleCallback(Handler.java:615)
E/WorkingMessage( 2245): at android.os.Handler.dispatchMessage(Handler.java:92)
E/WorkingMessage( 2245): at android.os.Looper.loop(Looper.java:137)
E/WorkingMessage( 2245): at android.app.ActivityThread.main(ActivityThread.java:4899)
E/WorkingMessage( 2245): at java.lang.reflect.Method.invokeNative(Native Method)
E/WorkingMessage( 2245): at java.lang.reflect.Method.invoke(Method.java:511)
E/WorkingMessage( 2245): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/WorkingMessage( 2245): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/WorkingMessage( 2245): at dalvik.system.NativeStart.main(Native Method)[/HIGH]

Here's the logcat. I looked back through the thread a bit and couldn't find exactly what fixed the mms stuff before. I might pick through Blood's MIUI stuff and see what he did to make it work there.

I think the uaprofurl setting can be found in the hidden data menu from a rom with a hidden menu. Back on like Page 16 I posted an apn fix for cm9 Aokp. May work for cm10

Since voice search isn't working, you will have to use an app like anycut to get to the apn settings
 
I think the uaprofurl setting can be found in the hidden data menu from a rom with a hidden menu. Back on like Page 16 I posted an apn fix for cm9 Aokp. May work for cm10

Since voice search isn't working, you will have to use an app like anycut to get to the apn settings

Still getting the same crash as before with the APNs fixed. It does seem like it's the same issue, but for whatever reason this didn't fix it.
 
Still getting the same crash as before with the APNs fixed. It does seem like it's the same issue, but for whatever reason this didn't fix it.

On cm9 I only had to fix the apn settings and the mms xml file. If the uaprofurl is missing from the stock messaging app, that may be something that would need to be extracted, decompiled, corrected, and recompiled. I'm not sure where else the uaprofurl is listed.

It may be built into the mms xml. If you look at a rom with a hidden menu you can get into the data menu from the dialer and the correct uaprof is listed under the browser tab. Not sure how you would change that without the hidden menu though.
 
On cm9 I only had to fix the apn settings and the mms xml file. If the uaprofurl is missing from the stock messaging app, that may be something that would need to be extracted, decompiled, corrected, and recompiled. I'm not sure where else the uaprofurl is listed.

It may be built into the mms xml. If you look at a rom with a hidden menu you can get into the data menu from the dialer and the correct uaprof is listed under the browser tab. Not sure how you would change that without the hidden menu though.


Can't remember which phone but it was in the smali of browserapk
 
I was poking around BloodDawns MIUI and I found his mms_config had a uaProfUrl string in the mms_config:

<string name="uaProfUrl">http://www.google.com/oha/rdf/ua-profile-kila.xml</string>

But it seems like that's not what's really used and that it should be listed elsewhere like you say
 
I havent't downloaded youtube onto my Marquee yet. I went on the browser and youtube was pretty fluid. No problems, no hiccups.

The only hiccup i receive is after turning off WiFi the Data sometimes doesn't kick back on until reboot. (Call me crazy, but it kind of seems like the wifi is disconnecting partially and causing the data to think the Wifi is still running).

Also, is tdm making a Kernel??? O.O Didn't know if i misunderstood anything.
 
Back
Top Bottom