-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Unofficial CM7 port, inquire within.
- Thread starter blarf
- Start date
-
- Tags
- lg optimus m
The APN config info is out of sync. It needs to be updated. I want to know what carrier the market thinks is associated with the MCC/MNC I picked so I know which to change.
Unsure if your MMS patch will work, but my guess is that it's overkill.
blaxican25
Android Expert
so joneidy when you gonna let us sample this rom lol ?
reppard
Android Enthusiast
I'm about to install linux on my gaming pc just so I can compile this rom. If a download isn't linked here today I probably will.
I'm looking at an MMS patch for the Optimus M. Maybe it's not yours. It includes SQLite, a snippet of SQL, and the whole MMS app. As far as I can tell all that needs to be changed are two values in an XML file (and then delete the database) or a couple of characters in a makefile. So yeah, that seems like overkill to me.
reppard
Android Enthusiast
No mms is a common issue with alot of custom roms and ports of roms. That includes official cm7 releases especially for metro PCS and cricket. That being said, a patched MMS.apk and database update post installation are required. You could compile the right database but you would still need a patched mms app. Sqlite is added simple to insure the latest version is being used. An update patch that is only a few megabytes and actually works can hardly be overkill.
blaxican25
Android Expert
watch how you talk to people barf lol rappards help alot of people before you showed up overkill.
reppard
Android Enthusiast
Haha I appreciate what he's trying to do and I am only trying to help advance this little project as I have had a little experience porting cm7 to this phone and have seen these issues first hand. Even compiling cm7 from scratch is going to take some post compiling modifications to get everything working.
Right and that's overkill for updating the database as it's populated by apns-conf.xml. It's it's just a matter of being able to authenticate with the MMS gateway, I'd be highly suspicious of needing a whole new MMS app. The way it stands now CM7 uses a different MNC/MCC combo that I've specified, so joneidy's build won't even see the MetroPCS entries already in CM7. I've already had to dick around with the VMU specific MMS stuff, which did not necessitate a new MMS app, and they actually do properly non-standard things.
The other reason I don't like the patch is that there are conflicting MNC/MCC values in the first entry, and the second entry doesn't change every field so it's dependent upon the existing database having certain contents.
So, yeah, overkill vs updating the XML and allowing the OS to repopulate the database itself. Another way to look at it is that simply working around the issue is counterproductive in determining what the root cause of MMS not working is.
Not necessarily, and that's kinda the entire point.
FTFY.
Welcome to my ignore list.
Okay no carrier means that the MNC/MCC settings I've used don't mean anything to Google. Try changing the requisite value in device_thunderc.mk (or just build.prop on your phone) from 310660 to 310027 and then rebuild/reinstall or reboot then clear your market data and login to the market from your phone again. If that's the right combo Google should recognize your phone as a MetroPCS phone within an hour (sometimes much less than an hour).
Using 310027 will pull the default settings from CM7 which were not even being looked at because I was using a different config. If that still doesn't get MMS fixed, post a logcat from around the time you're trying to send an MMS.
Note please don't do this after you've applied the patch.
KrazeeCracker
Android Enthusiast
Android?What!?
Android Enthusiast
Same here, been checking back for days.
Right now I'm completely dependent upon joneidy to give me feedback and merge this stuff back into the tree. If anyone else has more time and the hardware to get everything built, please have at it.
The wiki is here:
https://github.com/inferiorhumanorgans/android_device_lge_thunderc/wiki
And the official build thread for the Optimus V is here:
[ROM+Kernel] Inferior Human Organs unofficial CM7.1 - xda-developers
Unfortunately without one of these phones, a MetroPCS account, and timely feedback I can't do much testing. Right now what's missing are:
- a GPL compliant kernel
- proper MMS settings
- potentially a custom recovery
- eventually the stock GPS libraries
So, overall, small potatoes.
The wiki is here:
https://github.com/inferiorhumanorgans/android_device_lge_thunderc/wiki
And the official build thread for the Optimus V is here:
[ROM+Kernel] Inferior Human Organs unofficial CM7.1 - xda-developers
Unfortunately without one of these phones, a MetroPCS account, and timely feedback I can't do much testing. Right now what's missing are:
- a GPL compliant kernel
- proper MMS settings
- potentially a custom recovery
- eventually the stock GPS libraries
So, overall, small potatoes.
KrazeeCracker
Android Enthusiast
damn lol
Damn I'm so sorry man. I've been so busy that I barely have time to use my computer. I actually was planning on telling you what was my current status. Well after a while of testing everything works flawless except for mms that I can't receive or send any, and a lag after unlocking the device that in my opinion has to do with the kernel.
If I get some time, I will work on the issues and probably upload a test rom. So that people can test it and experience the new CyanogenMod. Lol
atownchevyboy
Well-Known Member
joneidy... you, blarf and reppard are awsome!!! we really appreciate you guys for working on this CM7 project, as you can see everybody's excited. get ready for 1000+ thank yous
reppard
Android Enthusiast
No luck with the mms patch? As for the kernel, it is essentially a stock kernel with some slight modifications in the CPU area so all should be well unless there is a library compatibility issue. Could be a simple setting in the build prop. I am hoping to get some internet soon so when I do I will download all the source and have a look and see what I can offer. I've pretty much stopped dev work until then cause I just can't stomach tethering anymore. Its very unproductive
No luck with the mms patch? As for the kernel, it is essentially a stock kernel with some slight modifications in the CPU area so all should be well unless there is a library compatibility issue. Could be a simple setting in the build prop. I am hoping to get some internet soon so when I do I will download all the source and have a look and see what I can offer. I've pretty much stopped dev work until then cause I just can't stomach tethering anymore. Its very unproductive
Sorry that I wasn't clear enough. With the patch I can only receive mms but not send. As long as I get at least an hour of free time ill work on that. And the screen its probably a library issue. I will also look into that. Lol
What happens ***WITHOUT THE PATCH*** if you change the MNC/MCC combo to 310660? If it doesn't work, post a logcat.
reppard
Android Enthusiast
BEGIN TRANSACTION;
UPDATE carriers
SET name='MetroPCS', numeric='311660', apn='', mcc='310', mnc='016', user='', proxy='proxy.metropcs.net', port='3128', mmsc='http://mms.metropcs.net:3128/mmsc', mmsproxy='', mmsport='', authtype='3'
WHERE _id = 1;
UPDATE carriers
SET numeric='310027', mnc='027', mmsc='http://mms.metropcs.net/mmsc'
WHERE _id = 2;
COMMIT;
Here are the parameters set in my sql file which updates the telephony database and should be the correct settings for our network
reppard
Android Enthusiast
I was simply offering WORKING parameters to the thread and not specifically addressing you. Please try to contain that flood of arrogance spewing forth from the depths of thine own self loathing. Thank you.