• 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

Whatvim noticing is that all sprint users have mms , but the boost phones do not. Can anyone confirm this? Its reminiscent of ctmod, and the need to flash a file for mms use.
 
k28king1 said:
Whatvim noticing is that all sprint users have mms , but the boost phones do not. Can anyone confirm this? Its reminiscent of ctmod, and the need to flash a file for mms use.
Click to expand...

My mms_config.xml for LG855 looks like this:

Code: 
<?xml version="1.0" encoding="utf-8"?>
<mms_config version="4">
    <bool name="enabledMMS">true</bool>
    <bool name="enableSplitSMS">true</bool>
    <int name="maxMessageSize">1048576</int>
    <int name="maxImageHeight">960</int>
    <int name="maxImageWidth">1280</int>
    <int name="defaultSMSMessagesPerThread">200</int>
    <int name="defaultMMSMessagesPerThread">20</int>
    <int name="minMessageCountPerThread">2</int>
    <int name="maxMessageCountPerThread">5000</int>
    <bool name="enabledTransID">true</bool>
    <int name="recipientLimit">40</int>
    <int name="smsToMmsTextThreshold">4</int>
    <string name="uaProfTagName">Profile</string>
    <!-- XXX: userAgent? -->
    <!-- XXX: uaProfUrl? -->
</mms_config>

Anything that needs changed?

(sorry I don't have this on github yet, I'm working on it...)
 
wallnutz said:
not to insult your intelligence, but did you do a factory,cache,dalvik wipe. i did before and after each flash of ics and gapps. and i have mms! btw im on sprint... i also fixed permisions, but that was before i checked if mms worked. so cant say if that did it.
Click to expand...
Haha. I'm not that sensitive. Yes I did do all you listed. I consider that standard before flashing anything. I'm on Boost. Seems most if not all boost users don't have MMS...
 
Flashed alpha 2 w/install.prop no problem and baseband now reads zv3. I noticed this build gave me the whole red carpet treatment opposed to alpha 1 that just showed me the door. I was hoping &#8220;roaming indicator off" would vanish too but hey you can't win em all huh lol.
 
tdm said:
Trying to get AOKP building. From the build errors, it doesn't look like AOKP supports any OMAP3 phones...?
Click to expand...

It does support omap although the aokp I used was an omap 4 on my kindle fire. Cm9 seemed a bit smoother than aokp on that. I imagine aokp simply works best on snapdragon s3 and s4 from what I've seen although I could be wrong.
 
realizm said:
Haha. I'm not that sensitive. Yes I did do all you listed. I consider that standard before flashing anything. I'm on Boost. Seems most if not all boost users don't have MMS...
Click to expand...

lol just saying, dont wanna step on any toes. but can other users confirm mms working or not. and would logs help decipher this bug?


and damn i have to learn how to use this so i dont have to double post, sorry folks...
 
tdm said:
My mms_config.xml for LG855 looks like this:

Code: 
<?xml version="1.0" encoding="utf-8"?>
<mms_config version="4">
    <bool name="enabledMMS">true</bool>
    <bool name="enableSplitSMS">true</bool>
    <int name="maxMessageSize">1048576</int>
    <int name="maxImageHeight">960</int>
    <int name="maxImageWidth">1280</int>
    <int name="defaultSMSMessagesPerThread">200</int>
    <int name="defaultMMSMessagesPerThread">20</int>
    <int name="minMessageCountPerThread">2</int>
    <int name="maxMessageCountPerThread">5000</int>
    <bool name="enabledTransID">true</bool>
    <int name="recipientLimit">40</int>
    <int name="smsToMmsTextThreshold">4</int>
    <string name="uaProfTagName">Profile</string>
    <!-- XXX: userAgent? -->
    <!-- XXX: uaProfUrl? -->
</mms_config>

Anything that needs changed?

(sorry I don't have this on github yet, I'm working on it...)
Click to expand...

Is your mms.XML identical to the stock xml? Have you tried to match the configuration from the boost mms fix? I think something is happening with the the new con figs that ics has... not as experienced with it as I would like. I will dig around see what I can find.
 
Don't know if any of this is useful in figuring out why boost mms doesn't work but figured I'd try something out
4257419f-a17b-9676.jpg

That's what shows up after SMS app FCs trying to send a MMS
 
tdm said:
My mms_config.xml for LG855 looks like this:

Code: 
<?xml version="1.0" encoding="utf-8"?>
<mms_config version="4">
    <bool name="enabledMMS">true</bool>
    <bool name="enableSplitSMS">true</bool>
    <int name="maxMessageSize">1048576</int>
    <int name="maxImageHeight">960</int>
    <int name="maxImageWidth">1280</int>
    <int name="defaultSMSMessagesPerThread">200</int>
    <int name="defaultMMSMessagesPerThread">20</int>
    <int name="minMessageCountPerThread">2</int>
    <int name="maxMessageCountPerThread">5000</int>
    <bool name="enabledTransID">true</bool>
    <int name="recipientLimit">40</int>
    <int name="smsToMmsTextThreshold">4</int>
    <string name="uaProfTagName">Profile</string>
    <!-- XXX: userAgent? -->
    <!-- XXX: uaProfUrl? -->
</mms_config>

Anything that needs changed?

(sorry I don't have this on github yet, I'm working on it...)
Click to expand...
The stock Mms.apk has a hidden_setting.xml in Mms.apk/res/xml, and in that file is
Code: 
srv_mms_url_set http://mm.myboostmobile.com

Not sure if it needs defined in the Boost version somewhere or not.
 
OK, just updated and I'm still able to get mms but cannot send.


I do believe that I've found my problem. I'll check back in a few when I get through trying something.


EDIT:
Nope. I was running the rooted Sprint version and went ahead and flashed ZV4 since I'm on Boost. Now it won't even download the MMS people send me. Wonder what's up with that. If anything, it should have helped it I would think. Oh well, I tried. LOL
 
  • Like
Reactions: tdm
@tdm, were you able to figure out the GPS thing by any chance, our is that still kinda hinged on the sprint stuff still?

And I flashed your latest build and it figured out my model automatically! That was pretty cool. Spectacular job on this ROM!
 
  • Like
Reactions: tdm
NeoSwagga said:
Flashed alpha 2 w/install.prop no problem and baseband now reads zv3. I noticed this build gave me the whole red carpet treatment opposed to alpha 1 that just showed me the door. I was hoping &#8220;roaming indicator off" would vanish too but hey you can't win em all huh lol.
Click to expand...

Make a backup, clear cache, flash this: http://tinyw.in/Bbd0 Then let me know if it worked ok.

rubble5dubble said:
@tdm, were you able to figure out the GPS thing by any chance, our is that still kinda hinged on the sprint stuff still?

And I flashed your latest build and it figured out my model automatically! That was pretty cool. Spectacular job on this ROM!
Click to expand...

I was able to use location yesterday, it used cell towers (not the actual gps) and was not completely accurate on my location but i was still able to get directions. It works good enough for what i need it for, im not one to drive with my phone telling me directions vocally, i just use it when i need it.
 
rubble5dubble said:
@tdm, were you able to figure out the GPS thing by any chance, our is that still kinda hinged on the sprint stuff still?

And I flashed your latest build and it figured out my model automatically! That was pretty cool. Spectacular job on this ROM!
Click to expand...

Nope, no gps yet.
 
Haven't had a chance to try new multirom until this morning. Page keeps timing out, The server at goo.im is taking too long to respond. Will try again later and let u know who it works on the AS855.

Edit: Downloading now.
 
I have found that if you use voltage control to set your overclock and save your boot settings as a init.d script and disable set on boot in the native cyanogen CPU settings and reboot, your oc settings seem to stick. At least voltage control reports that it does.
 
The~Skater~187 said:
I have found that if you use voltage control to set your overclock and save your boot settings as a init.d script and disable set on boot in the native cyanogen CPU settings and reboot, your oc settings seem to stick. At least voltage control reports that it does.
Click to expand...

I can confirm this. Although it does still stick to certain frequencies though. I have mine set at 1300-300 on demand, and it is stuck at 1300.
182e049a-15e6-00c2.jpg
 
lMonsterl said:
Mine unfortunately sticks to the bottom end of the spectrum. It's almost always at 300Mhz
Click to expand...

425753c9-31ba-838b.jpg
425753c9-31cc-3e8e.jpg


As you can see, mine stuck at 1300 for a while. It also accessed other frequencies at 1 second intervals although it doesn't stay the phone can access the other frequencies. I use voltage control, and I set to save boot settings as init.d.
 
You must log in or register to reply here.
Back
Top Bottom