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

Root [Boost Mobile] Let's Start A Team ROM!?

I forgot about that one, I didn't use MMS much and not at all on WIFI.


I dont want to replicate the same problem. Ill looks for another way. We could just use a play store app for mms. Until we resolve the underlying issue


I did notice that dev tools fc's when you running the mms test. Maybe if I pull apart dev tools I can find what it's looking for which in turn may point to the problem
 
For the record on alliance 3.1 I just got the best uptime I've ever seen by far. Until I shut it down today to do some recovery stuff it had been on without reboot for 4.5 days. I know on ctmod the phone rebooted itself at least once a day. And God knows how many times on stock lol.

You've got a very stable Rom here guys!
 
A really nice possible feature of the rom could be SMS scheduler :D maybe?

Edit: hey blyss, do you have 3g running on the phone at all? I'm trying to figure out how you got such life out of this phone xD
 
Can someone post a logcat of what happens when mms fails? I'd run it myself but I am doing a stability test on DS. I'm hoping for a week without a reboot for any reason.
 
A really nice possible feature of the rom could be SMS scheduler :D maybe?

Edit: hey blyss, do you have 3g running on the phone at all? I'm trying to figure out how you got such life out of this phone xD

Halfway through writing this I realized you might have misunderstood me. I didn't mean all that was on battery. Just that it was on that long without being rebooted or locking up etc.

No 3g. Remember I have no service. This is what those days consisted of:

Airplane mode on(so no wasting juice looking for a signal that isn't there)

Wi-Fi on about 75% of time.

GPS on for about 1 hour.

Plugged in about 75% of time.

In those 4.5 days it probably saw actual use time of 30 hours. Playing videos, listening to music, browsing web, posting here. A couple hours of gaming.
 
So guys as of now which is rhe mos stable rom?? Cuz i think i am running on alliance 3.5 and it aint let me use some apps they crash the phone freezes and a bunch of stuff more lol
 
So guys as of now which is rhe mos stable rom?? Cuz i think i am running on alliance 3.5 and it aint let me use some apps they crash the phone freezes and a bunch of stuff more lol


There are a few to pick from. In alphabetical order the most current stable roms are Droidsmith, Halo Jelly, and WOEM. All are contributors to alliance, but alliance is still in the alpha stages. Flash any of those three roms and I'm sure you'll be happy.
 
So guys as of now which is rhe mos stable rom?? Cuz i think i am running on alliance 3.5 and it aint let me use some apps they crash the phone freezes and a bunch of stuff more lol

There are a few to pick from. In alphabetical order the most current stable roms are Droidsmith, Halo Jelly, and WOEM. All are contributors to alliance, but alliance is still in the alpha stages. Flash any of those three roms and I'm sure you'll be happy.

All three of those roms are stable, but picking a rom isn't just about stability, its also about features, so remember to check that out before picking a rom, LowNSlow.
 
So guys as of now which is rhe mos stable rom?? Cuz i think i am running on alliance 3.5 and it aint let me use some apps they crash the phone freezes and a bunch of stuff more lol

And if your gonna go with alliance even though it's alpha, 3.1 is the most stable. Anything higher are test versions made to try to solve the MMS problem.
 
Does the mms_config.xml for pmi look anything like this?

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2009 The Android Open Source Project

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<mms_config>
<!-- Flag indicating whether MMS should be enabled -->
<settings
pref_key_auto_delete="yes"
pref_key_sms_delete_limit="500"
pref_key_mms_delete_limit="50"
pref_key_sms_delivery_reports = "no"
pref_key_sms_expiry = "245"
pref_key_mms_expiry = "691200"
pref_key_sms_priority = "0"
pref_key_mms_delivery_reports = "no"
pref_key_mms_read_reports = "no"
pref_key_mms_auto_retrieval = "yes"
pref_key_mms_retrieval_during_roaming = "no"
pref_key_mms_restricted_mode = "0"
pref_key_enable_notifications = "yes"
pref_key_edit_signature = ""
pref_key_enable_signature = "no"
pref_key_ringtone = "content://settings/system/notification_sound"
pref_key_max_message_size = "1048576"
pref_key_ua_agent = "Android-Mms/2.0"
pref_key_ua_prof_url = "http://www.google.com/oha/rdf/ua-profile-kila.xml"
pref_key_sms_to_mms_text_thread = "7"
pref_key_enable_box_mode = "no"
pref_key_enable_add_message_signature = "1"
pref_key_enable_sim_messages="0"
pref_key_enable_sms_priority="1"
pref_key_enable_sms_reassembly_display="1"
pref_key_enable_send_empty_message="1"
pref_key_enable_log_mode="no"
/>
</mms_config>
 
Does the mms_config.xml for pmi look anything like this?

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2009 The Android Open Source Project

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<mms_config>
<!-- Flag indicating whether MMS should be enabled -->
<settings
pref_key_auto_delete="yes"
pref_key_sms_delete_limit="500"
pref_key_mms_delete_limit="50"
pref_key_sms_delivery_reports = "no"
pref_key_sms_expiry = "245"
pref_key_mms_expiry = "691200"
pref_key_sms_priority = "0"
pref_key_mms_delivery_reports = "no"
pref_key_mms_read_reports = "no"
pref_key_mms_auto_retrieval = "yes"
pref_key_mms_retrieval_during_roaming = "no"
pref_key_mms_restricted_mode = "0"
pref_key_enable_notifications = "yes"
pref_key_edit_signature = ""
pref_key_enable_signature = "no"
pref_key_ringtone = "content://settings/system/notification_sound"
pref_key_max_message_size = "1048576"
pref_key_ua_agent = "Android-Mms/2.0"
pref_key_ua_prof_url = "http://www.google.com/oha/rdf/ua-profile-kila.xml"
pref_key_sms_to_mms_text_thread = "7"
pref_key_enable_box_mode = "no"
pref_key_enable_add_message_signature = "1"
pref_key_enable_sim_messages="0"
pref_key_enable_sms_priority="1"
pref_key_enable_sms_reassembly_display="1"
pref_key_enable_send_empty_message="1"
pref_key_enable_log_mode="no"
/>
</mms_config>

the mms_config.xml in the custom config or in the mms.apk? but yea it looks like the custom config version... where did you find this?

Well I was recently given an n861 for testing purposes and i found in the sequent that the custom config folder has a mms_conf.xml.. I'll have a test in a few... been a while hope we regain some of the lost momentum...
 
The apk is from ics so it wont work with alliance, but maybe a few mods to the posted configuration file will do the trick. No I have not tried it yet
 
ok but could you send? cause even that would be a step forward right now...


I think sending worked in 3.1. We need to consolidate our work. Mms or not call it alpha 4 and start a new thread. Chasing stuff down gets to be a pain. I'm willing to build it since I have the original base. Just point me to the different versions that I need along with what needs to be pulled from them. Alliance runs the ramdisk from DS with a few mods. I will be updating it in DS so I should update alliance as well. So far I'm at about 72 hours of uptime, and running smooth as it did right of boot. I figure at 100 he's DS moves to 1.7.3 and Alliance moves to a consolidated alpha 4
 
I think sending worked in 3.1. We need to consolidate our work. Mms or not call it alpha 4 and start a new thread. Chasing stuff down gets to be a pain. I'm willing to build it since I have the original base. Just point me to the different versions that I need along with what needs to be pulled from them. Alliance runs the ramdisk from DS with a few mods. I will be updating it in DS so I should update alliance as well. So far I'm at about 72 hours of uptime, and running smooth as it did right of boot. I figure at 100 he's DS moves to 1.7.3 and Alliance moves to a consolidated alpha 4

I think I figured out two solutions to fix what was going on with my theming when I was trying to do stuff for this rom, so I'll take a break from my rom and give theming this another shot now that I have a bit more knowledge.
 
Back
Top Bottom