For some reason, I'm getting issues when trying to install a modified Phone.apk. After I flash it, I am getting FC's everywhere, and the dialer won't even open, I also don't have any service, causing me to push the old one back.
Can anyone shed some light on the reason this is happening?
rp1783 said:
For some reason, I'm getting issues when trying to install a modified Phone.apk. After I flash it, I am getting FC's everywhere, and the dialer won't even open, I also don't have any service, causing me to push the old one back.
Can anyone shed some light on the reason this is happening?
Click to expand...
Click to collapse
Well first, the dialer is in the Contacts.apk not Phone.apk btu you would want to ensure they both match
rp1783 said:
For some reason, I'm getting issues when trying to install a modified Phone.apk. After I flash it, I am getting FC's everywhere, and the dialer won't even open, I also don't have any service, causing me to push the old one back.
Can anyone shed some light on the reason this is happening?
Click to expand...
Click to collapse
this has happened to me with certain apps (mainly Phone, Contacts, and Launcher) and it seems I get FCs when adb pushing it but it goes through properly when i stick it in an update.zip and flash it ... maybe try this way?
Related
I don't know if anyone else is having this problem, but for the longest time I haven't been able to send/receive MMS on my phone. I run recent CM6 nighties, with s-off, hboot .92 and the 7.28 radio. Right now using the ziggy 10-26 kernel.
I primarily use Handcent, but I've tried it in the stock messaging app too and nada!
It just keeps "sending..."
I've tried searching XDA, handcent forums, forums at Cyanogen, etc. Never really found anything helpful. If there's something I missed I'd greatly appreciate anyone pointing me in the right direction.
Any help would be appreciated!
Thanks in advance
cokm4n said:
I don't know if anyone else is having this problem, but for the longest time I haven't been able to send/receive MMS on my phone. I run recent CM6 nighties, with s-off, hboot .92 and the 7.28 radio. Right now using the ziggy 10-26 kernel.
I primarily use Handcent, but I've tried it in the stock messaging app too and nada!
It just keeps "sending..."
I've tried searching XDA, handcent forums, forums at Cyanogen, etc. Never really found anything helpful. If there's something I missed I'd greatly appreciate anyone pointing me in the right direction.
Any help would be appreciated!
Thanks in advance
Click to expand...
Click to collapse
This happened to me when I used Cyanogen as well. Never got it fixed. With this new rom (Ultimate Droid) when I deleted Mms.apk i couldn't receive so i restored it. Possible you don't have Mms.apk in /system/app/ ?
I checked, it's in there.... I'd really hate to go back to a sense rom in order to get mms to work. I'm surprised nobody else has had this problem...
Any other thoughts floating around out there?
Thanks again!
Make sure you don't have the stock messaging app disabled or any parts of it blocked or disabled. I had that problem before and that's what caused it.
Sent from my ADR6300 using Tapatalk
Thanks for the thought, but I don't think that's the problem either. I can send SMS through stock, but MMS keeps saying "Sending..."
I had this problem before as well. Spent HOURS upon HOURS trying to resolve it. Turned out it was a simple rule in my firewall, Droid Wall. Make sure you allow "Messages" access. Doh!
I have this problem as well. I can send/receive on any htc sense rom, such as stock or myn's 2.2, but cannot send on miui or cm6.
MIUI - no send/no receive
cm6 - yes receive / no send.
I really can't figure out what htc framework, or the mms.apk, has that is letting it that the others won't. It's strange.
I know this isn't much help as I cannot remember how exactly I fixed this but it is indeed fixable so do not give up. cyanogen 6.1 RC2 works fine it seems, have you tried the new one?
I'm on 6.1 rc2. So far I've tried....
replacing the apn with a known working apn
wiping everything/flashing cm6/replacing apn/rebooting
replacing apn with cyanogen's posted apns-conf.xml, deleting telephony folder, rebooting
any basically any combination like that.
edit: I even tried replaceing the telephony.db and apns-conf.xml on cm6 with the ones that were on my working stock sense rom. Still stuck at "sending"
Anyone ever get this figured out? Having the same issue on my g/f's Incredible. She can receive MMS just fine in stock Messaging and Handcent, but can't send MMS in either; just sticks at "sending..."
It's an issue in both CM6 & 7. We've wiped, checked APNs, checked mms.apk, etc.
Still plugging away at this, but no avails so far. =/
Cheers for any input.
Scratch that;
A full re-wipe and re-flash fixed it.
Even though I wiped going from Sense>CM6 (then 7) on her Incredible, it sort of seems like a lot of the Sense/Verizon settings were retained within the system - almost like the wipe didn't fully do its job.
When I first ran the new CM6 install last week, Google never pulled her apps or full contact info automatically. It honestly seems like those Verizon apps were f**king up her ability to properly sync contact and app data to her Gmail account, even though it was checked to do so. Now, after a week of running on CM, a full wipe and re-install has all of that info pulling down properly, as well as full restoration of the ability to send MMS.
Hope this helps some folks out there having this issue.
Byebye. =]
Alright, so I was trying to use a program that some other people have said work fine but it wouldn't work, so I figured I would unroot/reroot and see if it helped. I restored the phone to factory settings, used the instructions that are readily available here and other places to unroot my phone and rooted it using the manual method (just like I did the day I got my phone) and tried to set everything back up, but have run into a few problems.
1) Text messaging
-I have used Handcent for a long time on old phones, and used it just fine on this phone, but when I got my phone set back up, texts were coming in from the wrong people. I would get a text from PersonA, but it would show up as PersonB and when I responded it would go to PersonB. The only way that I could respond to PersonA was to back out, go into the people app, choose PersonA and text them. When I did this, it would take me into the exact same thread but have PersonA's name at the top now. When PersonA responded, it would show up as PersonB again and I would have to do it all over.
2) Google Wallet
-Was working fine, even used it at McDonald's, but now when I try to load it up for the first time, it sits at a black screen until eventually it says "Wallet is not responding. Would you like to close it? (Wait) (OK)"
Oh, and the program that I originally went through all of this for is still giving me the same error about not being able to locate a partition to remount to write to. What do I need to do to get this thing back to working correctly?
shane_huskey said:
1) Text messaging
-I have used Handcent for a long time on old phones, and used it just fine on this phone, but when I got my phone set back up, texts were coming in from the wrong people. I would get a text from PersonA, but it would show up as PersonB and when I responded it would go to PersonB. The only way that I could respond to PersonA was to back out, go into the people app, choose PersonA and text them. When I did this, it would take me into the exact same thread but have PersonA's name at the top now. When PersonA responded, it would show up as PersonB again and I would have to do it all over.
Click to expand...
Click to collapse
This is happening to me! I am rooted, completely stock otherwise and using Handcent. Is this a handcent issue? Anyone have more insight into this?
I'm in the process of unrooting my phone again to see if it happens when I'm not rooted.
Update:
Unrooted, same issue with Google Wallet and messaging
Rooted again, same issue
I was kindof hoping that someone would have come in here by now with some "here, try this" or "yeah, that happened to me and this is how I fixed it" type post. Am I the first person that has run across these issues after flashing to stock files from code.google.com?
I'm on 2nd nexus and haven't had that issue with handcent on either phones. Stock or rooted..
Sent from my Galaxy Nexus using XDA App
Are you uninstalling and reinstalling your apps? Have you tried deleting your apps' respective caches?
Sent from my Galaxy Nexus using XDA App
Well the 3 obvious problems could be:
1) I am either following the steps to unrooting incorrectly. (I don't think that it is rooting that is causing the problem since I a) didn't have the problem before I unrooted the first time and b) the problem is recreated whether I am rooted or not.)
2) My phone is faulty
3) The files that I am using (downloaded directly from http://code.google.com/android/nexus/images.html) are damaged.
The MD5 matches the .tgz file.
Everything looks like it is going through correctly when I am flashing the files.
I don't think that I am following the instructions in correctly, so that narrows it down (in my head anyway). Has anyone else used the factory images for code.google.com? Have you tried running Google Wallet afterwards?
esuohe said:
Are you uninstalling and reinstalling your apps? Have you tried deleting your apps' respective caches?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I have tried going into settings, force closing the app and clearing cache and I have tried resetting the phone to factory defaults. Neither changed how the app behaved. I still just get a black screen with the not responding message.
I did some more research into the Handcent problem, apparently it is fairly widespread on ICS and goSMS has the same issue. Stock is apparently not affected, so I am using that but it sucks...
I have seen a few of the GoSMS and Handcent posts, but I'm not completely sure that I am experiencing the same issue. Every post I have seen speaks of erratic problems. Mine is with every text message. Also, it didn't start happening until I flashed the factory images from code.google.com. Also, the problem only popped up when I started experiencing other problems (like with Google Wallet). Although we are having a similar issue, I believe the root problem of the issue is different, which is why the issues are slightly different.
Went and exchanged my phone today, rooted as soon as I walked in the door, installed everything back to the way that I had it and everything is working fine again. On my way to McDonald's for lunch.
I have tried on two phones to download the Battlenet Authenticator with no luck (the other phone is my EVO). I keep getting the message 'Your phone is not compatible.' I know it will work because it has happened with other apps. I cannot find the latest version of the app online. Would someone download, rip and email me the .apk?
Thanks for any help.
Have you changed your DPI? If so, change it back and clear the market data. that will fix your problem.
Wabem said:
Have you changed your DPI? If so, change it back and clear the market data. that will fix your problem.
Click to expand...
Click to collapse
Wow.. thanks. Fixed two issues at once. I had been wondering why my phone would do that, and I could not find the answer. I have been just downloading apps off the net then installing them.
Thanks again.
Hello there,
I'm relatively new to XDA but I've heard that pretty much any problem can be solved through you guys. So here we go. I have an original HTC Incredible (hence the title) which is rooted and has the Android Business Gingersense 2.3.5 ROM installed. My problem is hard to explain, yet may be very simple. I simply cannot send or receive text messages to my knowledge.
So here are the details. Whenever I compose a text message in the native "Messages" app, I click send and the "Loading..." little window with the spinny circle pops up for a split second, disappears and nothing happens. It doesn't show me that the message was sent, nor does it give me an error message saying that it didn't send. Nothing. I have heard, however, from the people I sent the messages to that some of them did in fact go through, but I just didn't know they did cause it didn't show up on my screen. They also said they texted me back multiple times trying to get a hold of me to no avail, which is the other problem. I also cannot receive any messages. It may be that these issues are connected in some way but I am not sure.
Another problem. My native email app has the same sort of issue, only when I compose a message and hit send, it force closes the app saying, "an unexpected problem has occurred." Therefore I cannot send or receive emails as well. Quite inconvenient as many of you probably know.
One last issue involving the texting problem. May not have anything to do with the native sms app, but I believe there is still a possibility. I mainly text with Pinger's TextFree application, which not surprisingly has the same problem as the native app. Every time I try to send a message, NOTHING happens, yet I get reports from the people I "sent" the message to that they actually got the message and tried to get back up with me multiple times. Still, I didn't receive anything. But I did go on the web based version of the app and saw both of our messages between each other and the web app worked fine.
Any help at all is greatly appreciated and I hope I can get this resolved.
Thanks alot!
Almost sounds like a data/mms config problem. Are you able to receive any messages or emails at all?
Sent from my ADR6300 using xda premium
Well, the weird part is, it goes on and off... like one minute I could receive SMS and email another minute I'm back to where I've been
Sent from my Droid using xda premium
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
ousuxndallas said:
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
Click to expand...
Click to collapse
Have you tried a complete wipe and reflash?
Shano56 said:
Have you tried a complete wipe and reflash?
Click to expand...
Click to collapse
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
ousuxndallas said:
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
Click to expand...
Click to collapse
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Open the stock messaging app then hit menu - settings - connection settings, there will be 5 settings greyed out in there. What are the current settings for those 5?
Edit: Nevermind i forgot were talking about cm9, might not the same settings as sense. Better yet go to the market and download "apn backup and restore", do a backup and then go to the sdcard then the apn backup folder and then open the xml backup with a text editor and copy and paste its contents to here. You are on verizon correct?
Shano56 said:
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Click to expand...
Click to collapse
Radio: baseband version 2.15.00.07.28
ousuxndallas said:
Radio: baseband version 2.15.00.07.28
Click to expand...
Click to collapse
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Shano56 said:
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Click to expand...
Click to collapse
Okay, I think I have figured it out. Before I reflashed, I deleted my Google account. Then, reflashed C9 and when prompted on reboot to sign into Google, I clicked "later".
So, now I received several test text messages I had sent the past 2 days.
So far, so good.
Also, when I restore from Titanium, I am only going to restore Apps, but not the System Data.
I think Google is somehow interfering with things. Maybe something funky with how my Google Voice is interacting with my phone. Who knows. Anyway, I will be sure to report back here to help others that may have similar problems.
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
ousuxndallas said:
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
Click to expand...
Click to collapse
haha yes. its never a good idea to restore system data
Hester topeico
One more follow-up. I now Restored all data for the apps separately through Titanium.
Texting still works.
I think when I flashed the new C9 ROM, when I restored Apps+Data in Titanium, something got screwed up and thus the texting function got screwed up.
Now able to send SMS texts but NOT receive them
I'm reviving this thread.
I have checked out a few other threads, and this comes the closest to describing my issues with my rooted unlocked (SEC OFF) HTC Droid Incredible (version 1).
I did NOT change ROMs -- right after getting the DINC, I installed a rooted stock deodexed GB 2.3.4 ROM from DINC.DOES-IT.NET, and I have not touched the ROM since.
BTW, the ROM build is 4.06.605.3 CL 140944 release-keys
Ditto baseband radios, no change. Version: 2.15.10.07.07
I did recently update the kernel to a version of gingertiny that allows apps to record phone conversations without the speakerphone being turned on.
Old version: 2.6.35.14-gingertiny-v2+ Feb 2012
New Version: 2.6.35.14-gingertiny-v2 Nov 6 2012
It is POSSIBLE that the problems started with the change of kernel, because I don't use texting very much at all, but that was still a few weeks ago.
Based on what I have read on XDA, I went into Clockwork Mod 5.x Recovery, deleted and reformatted the data cache, and rebooted.
After that, I could SEND but NOT RECEIVE text SMS.
I had some doubts about whether all my calls were ringing through properly. I am still not entirely sure, but test calls from a landline and mobile phone did ring the phone, so maybe that is no longer (or maybe was not ever?) a problem.
I have seen suggestions to do everything from reinstalling ROM (being sure to restore only apps+data, NOT system data) to flashing a new radio to running *228 over-the-air update to manually upgrading the PRL list.
And then there is the question I have about the kernel change somehow being the culprit...
EDIT: One other thing I did right before changing the kernel was run Convert2Ext4 v2.0 using the "no data limit normal dalvik" version. My reason for running this was to get rid of the low memory/no memory warnings, lockups and crashes I was expriencing despite having over 300MB left out of 775MB on internal memory.
How should I go about trying to restore the ability to receive SMS without totally bricking or otherwise disrupting my DINC and causing more harm than good?
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Some more details
tiny4579 said:
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Click to expand...
Click to collapse
Thanks for having a look in, Tiny.
I use PagePlus running off VZW towers. PagePlus service rep sent me an SMS while I was in contact with her by phone, she said it got deducted from by cash balance. The only thing is, it did not actually reach my phone!
I have only used the stock SMS app until just yesterday, when I installed Handcent SMS. That did not help. Will uninstall, but I doubt that will make a difference.
Will go back to the old gingertiny kernel and see what that does, and report back here.
If that doesn't do it, maybe it's time for a Touch of Blue ROM, with which many seem to be doing so wiell...
Is anybody else having trouble with the email force closing all he time? I'm on a rooted p600.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Rooted, no email problems, it's my most used app.
Enable My Magzine if you've disabled it. I read somewhere that it's somehow tied to the stock Mail App. Solved my Emal FC's.
meks007 said:
Enable My Magzine if you've disabled it. I read somewhere that it's somehow tied to the stock Mail App. Solved my Emal FC's.
Click to expand...
Click to collapse
That was one of the apps I deleted once I was rooted. Anyone know where I can get it?
I Love The Smell Of Burnt Rubber Anytime
I'd give you my backup, but I'm afraid that's odexd.Your best bet would probs be to extract it from a corresponding firmware package. Quick googling for it yielded no results.