Cool, I flashed my regular tethering app from stock and thought it would work on this rom but no go, But I am currently running evilkingdom rom v3 deodexed with your old aosp file that only changes the status and settings and everything works flawless. Nice rom by the way
After you guys flash this can you please post whether or not you have fully working mms?
first not working for me , i install again doin clean cache , format data cache , after that i just can recieve pic but dont send , well i flash you mms2.zip in now everything is working i can receive y send pics .
Last edited by jorgkrkmo; September 30th, 2012 at 10:58 PM.
first not working for me , i install again doin clean cache , format data cache , after that i just can recieve pic but dont send , well i flash you mms2.zip in now everything is working i can receive y send pics .
So I guess we can say mms is fixed......As far as the power button freezing the phone if you press it when it's ringing the only solution I have as of right now is to press a volume button instead.
I just began looking at the ROM files and wondering if mms is only working for the Boost people. I have not installed it as my Hero S no longer has service as I changed phones. But the build.prop is set to Boost, and the apns.xml in the framework-res.apk is set to boost.
Can someone confirm either Sprint or US Cell working mms?
I just began looking at the ROM files and wondering if mms is only working for the Boost people. I have not installed it as my Hero S no longer has service as I changed phones. But the build.prop is set to Boost, and the apns.xml in the framework-res.apk is set to boost.
Can someone confirm either Sprint or US Cell working mms?
This Rom was written for boost only but it would probably work on sprint with no modification. The build prop on my warp had all sprint info and the sprint prls would work as well. Mms was still not working even with the stock framework file aNd other carrier specific files. The way I got it to work was with the TB tar.gz with the contents of the file_parts folder removed. TB shows it as dialer storage and in the backup its com.android.providers.telephony. after digging around I think the removal of the stock browser broke mms. HTC puts checks in everywhere.
This Rom was written for boost only but it would probably work on sprint with no modification. The build prop on my warp had all sprint info and the sprint prls would work as well. Mms was still not working even with the stock framework file aNd other carrier specific files. The way I got it to work was with the TB tar.gz with the contents of the file_parts folder removed. TB shows it as dialer storage and in the backup its com.android.providers.telephony. after digging around I think the removal of the stock browser broke mms. HTC puts checks in everywhere.
There is a slight difference in mms settings for the sprint and boost specoficaly the server not sure if they are interchangeable. I loaded the Rom on my dead phone to check it out. Quite impressed still some bloat left. I will play with it for today and upload it and send you a link for you to test out. The bloat o am refering to is not apps but dead files in /etc and customize
The build.props should be edited for each carrier if you want it to interchange. All I want is to know if anyone in sprint or uscc has tried the Rom and their input on mms and the market as also.
Last edited by cookiefrog; October 1st, 2012 at 11:16 AM.
There is a slight difference in mms settings for the sprint and boost specoficaly the server not sure if they are interchangeable. I loaded the Rom on my dead phone to check it out. Quite impressed still some bloat left. I will play with it for today and upload it and send you a link for you to test out. The bloat o am refering to is not apps but dead files in /etc and customize
The build.props should be edited for each carrier if you want it to interchange. All I want is to know if anyone in sprint or uscc has tried the Rom and their input on mms and the market as also.
With some things not working I was trying notto go too overboard on the deleting of things. It does need some cleaning up, i agree....The google now is bloated as hell but 80 % of it or more is libs and usr language and speech files...It seems like a pretty useful program though for its space its using, better than the pitt patt crap anyways IMO.
There is a slight difference in mms settings for the sprint and boost specoficaly the server not sure if they are interchangeable. I loaded the Rom on my dead phone to check it out. Quite impressed still some bloat left. I will play with it for today and upload it and send you a link for you to test out. The bloat o am refering to is not apps but dead files in /etc and customize
The build.props should be edited for each carrier if you want it to interchange. All I want is to know if anyone in sprint or uscc has tried the Rom and their input on mms and the market as also.
I can confirm MMS still is not working for sprint but market is fine.
What a giant mess. Like what you are trying to do but as I mentioned to you before in one of my messages I would start new from the ground up and implement everything fresh instead of from a backup. Yeah it will be hard work but you will only get the fluidity and cross carrier functionality this way. I went and changed decompiled some apks, changed a few things and had someone test them for me. I then browsed the file structure and saw allot of stuff that makes no sense and not even sure how it got to be that way. Here are some examples;
in the system/etc directory there is a apn.conf file. not sure what purpose this even serves. On AOSP ROMS the apns-conf.xml resides in system/etc but this file is just a plaintext file in your ROM it is not designated as an .xml not sure if your mms application is trying to read the APNs from this file as AOSP would do or from where, surely it is not reading them for mms from framewrok-res.apk as I did edit the apns.xml in that apk, and also modified the build.prop with a few other changes to see what would work.
Also you have a system/etc/init.d folder but in system/etc you have three scripts just floating in there, not sure what they do or what purpose they serve or even if they are being called by anything. One of them is for the quemu emulator and setting ip settings on an ethernet interface.
There is so much more that i could write here, one question I thought you where running the v4 kernel on the ROM, my system information showed the stock htc kernel.
Anyway, here is where I am coming from. When i began doing developing I was very harshly criticized by some of the devs (one in particular I will not mention but who I owe allot to). Please understand that I am not trying to discourage you. On the contrary I am trying to push you to accomplish what you truly want and that is to excel in your development work. Easy fixes and what i call the cut and paste method of developing will always keep you running like a chicken with your head cut off. Because one fix will probably break something else along the way. Back in another forum I saw a Dev trying to load his ROMs with so much stuff to make them attractive that he ended up just making a mess of what he had.
I owe 2fast allot, but one thing i learned from him that has been the best lesson i learned is the way to develop a ROM from a base. You would be surprised how much time and effort it takes, but if you looked at the files in xfuzzion, iced speed, etc you will see a cleanliness though out that is a reflection of the work spent. I dont have the Hero S activated (I exchanged phone models last week) so i can not troubleshoot the mms issue for you to find out what in the world is going on, your fix might work but in my opinion it is not the cleanest and thus why I was wanting to look at this. So for you and any other person reading this here is some wisdom i learned and whoever wants to use it can and whoever does not then oh well....
First and foremost LOG WHAT YOU ARE DOING! Keep a text file on what changes you are doing to the ROM...this is so valuable in the future, specially when making smali edits, also it helps you keep a rack of things. While we worked on IcedSpeed, the developers logged changes and then uploaded the commits to a central ftp server where we would be able to check out the newest version and also read the work included by the developers themselves. IcedSpeed went through like 12 revisions in about 3 weeks of many hours before it went public. Always have testers for each carrier, be patient (2fast taught me that quite well, as I was always ready to move on but he was never satisfied with the result just yet...at the end I realized that this was a crucial virtue to have)
Begin with your base ROM, and debloat, this means not just your apks, but for example sense has all the ebooks under /etc and allot of junk in resources/customize. go through the file structure and get rid of all the added junk to the phone. Now get the basics working before adding anything else. MMS, 4G, ADB, USB storage, work on each one at a time, and make sure they are working before moving on. DONT go easy on problems, have it working the right way, not by some half @$$ hack. This will help you understand how it all works together and will increase the know how for your own benefit. include the kernel you are using on your skeleton.
Now after the skeleton is working then add your APM, and other features like beats, and what else you want...take your time work out the bugs with patience. Always have your testers give feedback. Good testers are hard to find. the ones that break everything are the best.
It takes allot of work. Trust me I did not just take 30 minutes out my day to barage you. The opposite. Take it for what its worth. Get some testers. Pull the ROM for a few weeks work on it from the ground up again, learn a few things along the way. When you are ready to relaunch it will be all you ever wanted it to be and then more, not only that, when anyone has an issue 9 out of 10 you will know exactly if it is an ID-10-T issue or a real issue with the ROM.
If I knew what had been done and where I would be much help with it, but as i look at the spaghetti mess I see in the file structure I cringe and just want to yell. its like walking into an episode of hoarders...lol I like what you are doing, not sure how it would end up if you started new, but I encourage you to redo it all from the base as I did in the past and build it all from the ground up again....
im on boost mobile, at first mms only received not send... flashed the mms2.zip and after wiping cache and delvik and fixing permissions 2x all is working fine
Alot of the mess in there is a result of trying to fix mms. I know there are better ways of doing this but with the limited time I have and my phone being my business line I do the best with what I have. I'll hit you up later ....
What a giant mess. Like what you are trying to do but as I mentioned to you before in one of my messages I would start new from the ground up and implement everything fresh instead of from a backup. Yeah it will be hard work but you will only get the fluidity and cross carrier functionality this way. I went and changed decompiled some apks, changed a few things and had someone test them for me. I then browsed the file structure and saw allot of stuff that makes no sense and not even sure how it got to be that way. Here are some examples;
in the system/etc directory there is a apn.conf file. not sure what purpose this even serves. On AOSP ROMS the apns-conf.xml resides in system/etc but this file is just a plaintext file in your ROM it is not designated as an .xml not sure if your mms application is trying to read the APNs from this file as AOSP would do or from where, surely it is not reading them for mms from framewrok-res.apk as I did edit the apns.xml in that apk, and also modified the build.prop with a few other changes to see what would work.
Also you have a system/etc/init.d folder but in system/etc you have three scripts just floating in there, not sure what they do or what purpose they serve or even if they are being called by anything. One of them is for the quemu emulator and setting ip settings on an ethernet interface.
There is so much more that i could write here, one question I thought you where running the v4 kernel on the ROM, my system information showed the stock htc kernel.
Anyway, here is where I am coming from. When i began doing developing I was very harshly criticized by some of the devs (one in particular I will not mention but who I owe allot to). Please understand that I am not trying to discourage you. On the contrary I am trying to push you to accomplish what you truly want and that is to excel in your development work. Easy fixes and what i call the cut and paste method of developing will always keep you running like a chicken with your head cut off. Because one fix will probably break something else along the way. Back in another forum I saw a Dev trying to load his ROMs with so much stuff to make them attractive that he ended up just making a mess of what he had.
I owe 2fast allot, but one thing i learned from him that has been the best lesson i learned is the way to develop a ROM from a base. You would be surprised how much time and effort it takes, but if you looked at the files in xfuzzion, iced speed, etc you will see a cleanliness though out that is a reflection of the work spent. I dont have the Hero S activated (I exchanged phone models last week) so i can not troubleshoot the mms issue for you to find out what in the world is going on, your fix might work but in my opinion it is not the cleanest and thus why I was wanting to look at this. So for you and any other person reading this here is some wisdom i learned and whoever wants to use it can and whoever does not then oh well....
First and foremost LOG WHAT YOU ARE DOING! Keep a text file on what changes you are doing to the ROM...this is so valuable in the future, specially when making smali edits, also it helps you keep a rack of things. While we worked on IcedSpeed, the developers logged changes and then uploaded the commits to a central ftp server where we would be able to check out the newest version and also read the work included by the developers themselves. IcedSpeed went through like 12 revisions in about 3 weeks of many hours before it went public. Always have testers for each carrier, be patient (2fast taught me that quite well, as I was always ready to move on but he was never satisfied with the result just yet...at the end I realized that this was a crucial virtue to have)
Begin with your base ROM, and debloat, this means not just your apks, but for example sense has all the ebooks under /etc and allot of junk in resources/customize. go through the file structure and get rid of all the added junk to the phone. Now get the basics working before adding anything else. MMS, 4G, ADB, USB storage, work on each one at a time, and make sure they are working before moving on. DONT go easy on problems, have it working the right way, not by some half @$$ hack. This will help you understand how it all works together and will increase the know how for your own benefit. include the kernel you are using on your skeleton.
Now after the skeleton is working then add your APM, and other features like beats, and what else you want...take your time work out the bugs with patience. Always have your testers give feedback. Good testers are hard to find. the ones that break everything are the best.
It takes allot of work. Trust me I did not just take 30 minutes out my day to barage you. The opposite. Take it for what its worth. Get some testers. Pull the ROM for a few weeks work on it from the ground up again, learn a few things along the way. When you are ready to relaunch it will be all you ever wanted it to be and then more, not only that, when anyone has an issue 9 out of 10 you will know exactly if it is an ID-10-T issue or a real issue with the ROM.
If I knew what had been done and where I would be much help with it, but as i look at the spaghetti mess I see in the file structure I cringe and just want to yell. its like walking into an episode of hoarders...lol I like what you are doing, not sure how it would end up if you started new, but I encourage you to redo it all from the base as I did in the past and build it all from the ground up again....
best of luck
There are some files that need to be cleaned up but we are talking a very minimal amount of crap. The scripts you speak of can be found in almost any other ROM like the goldfish one you mentioned. The mms fix is a "patch" but you will not find too many desensed roms with working MMS period.
What this ROM needs is a new Settings.apk to get rid of some of the remaining bugs. There are probably some lib files not being used as well but they were not worth messing with and breaking something.
yes there are apks from different phones and versions but they were the most functional versions.
I would like to learn how to decompile and modify some of the internals but that I have not had the time for.
honestly this ROM is 100% more functional than the CM9 or 10 releases for this phone and outperforms both in every category function wise, hands on wise and with better performance. I like my 4g, bluetooth,GPS and all the other features I bought the phone for and everyone of those things are working as of right now and if I stripped the extras off like the unneeded google apps and other optional stuff you would still have a fully functioning ROM with a zip size of less than 140 MB
Device(s): Droid X with MIUI,
Motorola Droid with CM7,
Galaxy Prevail with CM7,
Epic 4G with MIUI,
ZTE Warp
Carrier: Not Provided
Thanks: 34
Thanked 66 Times in 50 Posts
I tried out this rom, but it seems that force closing apps is broken, can't even do it with titanium. I need that ability for Google voice to retry sending texts. Also, the hot reboot option didn't work.
I did a factory reset and formatted /system before flashing.
I tried out this rom, but it seems that force closing apps is broken, can't even do it with titanium. I need that ability for Google voice to retry sending texts. Also, the hot reboot option didn't work.
I did a factory reset and formatted /system before flashing.
which version of the rom , what rom are you coming from and who is your carrier?
Device(s): Droid X with MIUI,
Motorola Droid with CM7,
Galaxy Prevail with CM7,
Epic 4G with MIUI,
ZTE Warp
Carrier: Not Provided
Thanks: 34
Thanked 66 Times in 50 Posts
I'll try it asap.
As for the future, do you have any plan to add the ability to kill an app with a long-press of the back button? It's a really big deal for me since I use Google voice
I'll try it asap.
As for the future, do you have any plan to add the ability to kill an app with a long-press of the back button? It's a really big deal for me since I use Google voice
I will look into it. Send me a link to a sense based rom that has the feature so I can decompile it and see what can be done.
That wipe will take about 10 minutes but is a must when going between JB and ICS
That wipe will take about 10 minutes if you have had a shitload of ROMS on your phone. If by some chance it doesn't work then put aLogcat on your phone and mail me the copy of the logcat so I can see what the problem may be.
Device(s): Evo 3d. Evo 4g. Galaxy SII. Nexus S 4g. Galaxy Prevail (the most loved)
Carrier: Boost Mobile
Thanks: 61
Thanked 320 Times in 197 Posts
I tried AOSensePvG3 last night. Calls and text work. 3g also worked. As someone suggested before it was as simple as turning data on after flashing. It seems to have been turned off during the process. MMS didn't work though. Not sure what the issue was data was working. Web pages loading and everything. Can sign into google and get my contacts synced etc.
MMS starts sending and says sending next to it but never actually sends.
I have a Sprint Design flashed over to Boost so it might be that. I didn't read about the aLogcat before I wiped if off my phone but if I reflash it over I'll do that.
I tried AOSensePvG3 last night. Calls and text work. 3g also worked. As someone suggested before it was as simple as turning data on after flashing. It seems to have been turned off during the process. MMS didn't work though. Not sure what the issue was data was working. Web pages loading and everything. Can sign into google and get my contacts synced etc.
MMS starts sending and says sending next to it but never actually sends.
I have a Sprint Design flashed over to Boost so it might be that. I didn't read about the aLogcat before I wiped if off my phone but if I reflash it over I'll do that.
I'm an the phone that i bought for boost so it should work but it doesn't. temp fix for me has just been using gosms as it works. only real bug I've noticed other than the mms is my 3g goes down to 1x sometimes and than cuts completely off other times.
I tried AOSensePvG3 last night. Calls and text work. 3g also worked. As someone suggested before it was as simple as turning data on after flashing. It seems to have been turned off during the process. MMS didn't work though. Not sure what the issue was data was working. Web pages loading and everything. Can sign into google and get my contacts synced etc.
MMS starts sending and says sending next to it but never actually sends.
I have a Sprint Design flashed over to Boost so it might be that. I didn't read about the aLogcat before I wiped if off my phone but if I reflash it over I'll do that.
Quote:
Originally Posted by APOPHiS420
I'm an the phone that i bought for boost so it should work but it doesn't. temp fix for me has just been using gosms as it works. only real bug I've noticed other than the mms is my 3g goes down to 1x sometimes and than cuts completely off other times.
There is a working fix for mms in this thread. Make sure you use the 4g widget so u know if your wimax is on with a weak signal
Device(s): Samsung Galaxy Pervail, HTC Evo Design 4g, Kindle Fire HD 8.9
Carrier: Not Provided
Thanks: 39
Thanked 12 Times in 12 Posts
Quote:
Originally Posted by HaydenM
There is a working fix for mms in this thread. Make sure you use the 4g widget so u know if your wimax is on with a weak signal
Could you Put the MMS fix link into the OP and maybe put a date for most recent the Rom was updated in the Main post Title.
Also another things not too major but 4g Does work but would be kinda nice if it would say the bars of reception and if its active in the task bar, not super important I guess, also is their a way to have it go right to the section with the settings instead of the other one first without the settings?
Could you Put the MMS fix link into the OP and maybe put a date for most recent the Rom was updated in the Main post Title.
Also another things not too major but 4g Does work but would be kinda nice if it would say the bars of reception and if its active in the task bar, not super important I guess, also is their a way to have it go right to the section with the settings instead of the other one first without the settings?
I'll fix the OP....Not sure what you are talking about with the "going to the other one first" so get back to me on that. I am working on getting a 4g icon in the task bar and possibly into the settings menu which will be a challenge. I havent seen any AOSP settings menu or status bar with 4g indicators that actually work for obvious reasons....I am learning the decompiling and compiling as I type...Just had my first success with a little status bar mod which I will post as well....I had a systemUI with working USB storage mode and another with transparent background and was able to put both together and recompile with no problems. Nothing major I know but its a step forward.
There are some files that need to be cleaned up but we are talking a very minimal amount of crap. The scripts you speak of can be found in almost any other ROM like the goldfish one you mentioned. The mms fix is a "patch" but you will not find too many desensed roms with working MMS period.
What this ROM needs is a new Settings.apk to get rid of some of the remaining bugs. There are probably some lib files not being used as well but they were not worth messing with and breaking something.
yes there are apks from different phones and versions but they were the most functional versions.
I would like to learn how to decompile and modify some of the internals but that I have not had the time for.
honestly this ROM is 100% more functional than the CM9 or 10 releases for this phone and outperforms both in every category function wise, hands on wise and with better performance. I like my 4g, bluetooth,GPS and all the other features I bought the phone for and everyone of those things are working as of right now and if I stripped the extras off like the unneeded google apps and other optional stuff you would still have a fully functioning ROM with a zip size of less than 140 MB
Ill post one if you would like.
I'm not going to bash you or anything so don't take it like that. How ever if cookie stepped out to help you and point you in the right direction. I wouldn't for say argue with him, if he points out issues then I would possibly look at them as he says. Some of the bloat I believe he is talking about is some images and such. Where in all honesty I would have removed that stuff first. Basically debloat the base you used till you break something and start from that.
As for your reply back I would never mix stuff from multiple phones. You will never be able to track down a bug or a issue you have when doing so. The scripts you speak of, I don't know what they are so I can't comment on that part. How ever you are comparing apples to oranges against my cm10 build or the evervolv build we did. I didn't take some rom and try to make aosp. It is built from clear scratch, where of course features aren't going to work. As it was the first build fixing stuff to get working then I stopped.
I'm not going to bash you or anything so don't take it like that. How ever if cookie stepped out to help you and point you in the right direction. I wouldn't for say argue with him, if he points out issues then I would possibly look at them as he says. Some of the bloat I believe he is talking about is some images and such. Where in all honesty I would have removed that stuff first. Basically debloat the base you used till you break something and start from that.
As for your reply back I would never mix stuff from multiple phones. You will never be able to track down a bug or a issue you have when doing so. The scripts you speak of, I don't know what they are so I can't comment on that part. How ever you are comparing apples to oranges against my cm10 build or the evervolv build we did. I didn't take some rom and try to make aosp. It is built from clear scratch, where of course features aren't going to work. As it was the first build fixing stuff to get working then I stopped.
I agree with what you say 100%. The last version I posted with everything removed is completely functional and has all the extra crap taken out which some people prefer and is what I've been running on my phone since I posted it with zero issues. I am still working on cleaning up the unused images and that will take some time. My only point with the comment on cm10 was speaking of its functionality and functionality in the near future, not of anyone's ability in getting it to where it is or where it needs to go. There is no doubt in my mind that you are the most knowledgeable person on this platform and the reason why the phone is where it is right now. The ROM I put out was based on your ROM and wouldn't even boot without the modded framework.jar. I decompiled it to see what was done to learn from it and I am at the point right now where I can do those things to an extent but you laid the groundwork.
Cookie contacted me and is willing to help but with my work schedule the way it has been and the time zone difference, It hasn't been possible. Therefore I have worked on it myself and IMO have done a good job on it. If this platform is going to continue to be developed it is going to come from more than one group and more people needing to get involved.
The debloated 117 Mb base was a great place to start for anyone wanting to get involved but nothing as of yet. You don't see too much out there in that size ROM that works and especially one that contains your basic Gapps to get going. It is a lot of work and a headache to self teach yourself everything but I've learned a lot i a couple of months. It is pretty obvious nothing is going to come from the jack asses that stirred up shit at SDX and this forum was starting to look the same so I stepped in and took some initiative....It would be great to have you guys involved in this project as I think it has a ton of potential and plenty of interest so far, just needs a little more knowledge and time.
Anyways, welcome back if you're up and running again....
Hi, just wanted to post an annoying (but easily able to work-around) problem. Some of my contacts have a plus sign before the phone number. If I try to call any of those numbers, I get a "Call has been lost" message and it doesn't call. I can obviously delete the +. Not sure if this has any larger implications. (Boost mobile, with Rev 3 of the AOSP rom)
Device(s): Samsung Galaxy Pervail, HTC Evo Design 4g, Kindle Fire HD 8.9
Carrier: Not Provided
Thanks: 39
Thanked 12 Times in 12 Posts
Quote:
Originally Posted by HaydenM
Not sure what you are talking about with the "going to the other one first" so get back to me on that.
Sorry didn't say that very clearly, I mean is their a way so when you open the status bar that it shows the Toggles right away and don't have to click the settings/toggle button. Thanks! Keep up the great work!
For some reason after flashing the new db version my gmail contacts aren't syncing to my phone. I tried reflashing and still same thing. I also wiped everything manually. Any ideas?
For some reason after flashing the new db version my gmail contacts aren't syncing to my phone. I tried reflashing and still same thing. I also wiped everything manually. Any ideas?
Is your Gmail account showing up under accounts and sync in your settings?
Great work on the rom first off. I noticed its been updated but don't see the updated file? Was the base rom just updated or the others as well?
Could you tell us what is the update.I don't see it either. by the way still running with no issues, love all the blue but any Chance to make a zip that could just change status bat icons to white? Lol I don't wanna be annoying so if not it cool.still love this ROM...GREAT JOB...
Device(s): HTC Evo Design 4G, Samsung Galaxy Prevail
Carrier: Not Provided
Thanks: 18
Thanked 40 Times in 33 Posts
Quote:
Originally Posted by HaydenM
Is your Gmail account showing up under accounts and sync in your settings?
The Rom has "GoogleContactsSyncAdapter.apk" removed from it along with a couple other nifty things to have such as "voicedialer.apk" so you can open up the APNs menu for if your mms isn't working (had this issue myself, copied them out of the vG3 rom. Moving them to /system/app in the Rom (can not install from within the rom as it is a System app) caused no issues and allowed me to sync contacts just fine. checking my APN settings now because it seems as if i can not send MMS (im on boost) however i can receive them. I'm double checking to make sure, will edit this post after i find out the results.
However the point of the post is, the only thing that WILL be able to sync without adding in that apk is gmail. (i'd imagine you'll probably add this apk back in for the next Rom, however for those who didn't know or would like to fix it themselves, there ya go )
EDIT: I'm having issues getting the APN to stick. Again i'm on boost mobile, no APN is shown in the APN's menu.
EDIT.. AGAIN: I tried the MMS fix, However it shows that its sending to some 760 number instead of my contact?
Also i let my poweramp app sit overnight on "installing".. reinstalled rom, tried again, still no luck.. I'm going to switch to your vG3 one and see if i still have this issue.
Same issue with the vg3 rom.. :/.. I'm going to try pushing it into the rom as a system app and see what that does for it.
Nothing i tried worked :/
Last edited by Travisholt92; October 10th, 2012 at 06:47 PM.
The Following User Says Thank You to Travisholt92 For This Useful Post:
The Rom has "GoogleContactsSyncAdapter.apk" removed from it along with a couple other nifty things to have such as "voicedialer.apk" so you can open up the APNs menu for if your mms isn't working (had this issue myself, copied them out of the vG3 rom. Moving them to /system/app in the Rom (can not install from within the rom as it is a System app) caused no issues and allowed me to sync contacts just fine. checking my APN settings now because it seems as if i can not send MMS (im on boost) however i can receive them. I'm double checking to make sure, will edit this post after i find out the results.
However the point of the post is, the only thing that WILL be able to sync without adding in that apk is gmail. (i'd imagine you'll probably add this apk back in for the next Rom, however for those who didn't know or would like to fix it themselves, there ya go )
EDIT: I'm having issues getting the APN to stick. Again i'm on boost mobile, no APN is shown in the APN's menu.
EDIT.. AGAIN: I tried the MMS fix, However it shows that its sending to some 760 number instead of my contact?
Also i let my poweramp app sit overnight on "installing".. reinstalled rom, tried again, still no luck.. I'm going to switch to your vG3 one and see if i still have this issue.
Same issue with the vg3 rom.. :/.. I'm going to try pushing it into the rom as a system app and see what that does for it.
Nothing i tried worked :/
For mms try restoring your 'dialer storage' in TB from a rom that was working. t
The apn setting screen has nothing to do with mms in a sense rom and I think it may be tied into the stock browser. I haven't had time to really get into it and try to fix anything and if you want to get more involved with this Rom I would really welcome some help. You may want totry the kingdomsuperwipe I posted before trying anything else. Pm me and I'll send you theRom I've been running which I've cleaned up a little more.
Device(s): Droid X with MIUI,
Motorola Droid with CM7,
Galaxy Prevail with CM7,
Epic 4G with MIUI,
ZTE Warp
Carrier: Not Provided
Thanks: 34
Thanked 66 Times in 50 Posts
Quote:
Originally Posted by HaydenM
I will look into it. Send me a link to a sense based rom that has the feature so I can decompile it and see what can be done.
That wipe will take about 10 minutes but is a must when going between JB and ICS
That wipe will take about 10 minutes if you have had a shitload of ROMS on your phone. If by some chance it doesn't work then put aLogcat on your phone and mail me the copy of the logcat so I can see what the problem may be.
34Likes
.
