Database Develop

SMS Backup:

Is anyone else unable to use this on the latest couple of CM builds?
It seems to always force close on me, going to try to get a log and maybe pass it on to the developer of the backup application...

One of my main reasons for not switching builds is because the lack of being able to backup and restore my sms.
I use sms backup and restore.
Works great.
Really great.
5,000 texts backed up to my sd card.
When I want to backup more sms they add to the data file or making more files in the folder.
and I've restored all my texts to three different builds now.
Last back up I did was on a new Dwang build, and for 4k and some odd hundred texts took about 34 minutes to restore in my inbox but it did perfectly.

the author of sms backup is aware of the issue. he's working on it.

bengrulz said:
the author of sms backup is aware of the issue. he's working on it.
Click to expand...
Click to collapse
Oh sweet, that's excellent - thanks for the heads up. : )

I'm looking into it as well. I'm not sure what broke it yet.

Just found the issue #50 in the google code page. Looking forward to seeing it fixed, one of the most useful (even if never used) features.
Being able to do a quick Google search on your sms messages is phenomenal. = )

I was having the same issue so I was about to contact with the dev but checked here first. Thanks for the advise!

The developer does not run CM, and as such is having a hard time replicating the problem, or getting enough information to figure out how to fix it.

SMSBackup is a must for me, as much as I text. When it broke, I started looking for alternatives.
XArchive is a similar app (based on the same source originally, I think), and it works fine on the latest CM builds. It's a pay app, but it works, so I bought it. No problems. I just couldn't wait for the free app to be fixed.

there is small fix here, works for me:
http://code.google.com/p/android-sms/issues/detail?id=50

An update was pushed today and the issue is now fixed! All is right with the world again!

Did everyone get up and running again with the latest update (1.1.1)? Because I'm still getting FCs, on 4.2.7.1 and 4.2.8, despite uninstalls and a wipe of the phone before 4.2.7.1.
Seriously bummed here, that's one of my favorite apps...
Ugh - of all the things I tried, I missed the most obvious... The folder name is case sensitive. D'oh!

Swype Beta Issue "Limited Functionality"

Hello All,
I am attempting to work with Swype support, as I keep getting stuck in the DRM with the beta, which disables the product and pops up "registered on another device, limited functionality", etc.
They have said they have tested it throughly, and have been "unable" to recreate the issue.
I would like to show them how many people are experiencing this issue, and have simply abandoned the beta, and have gone back to the WORKING leaked prerelease.
Please post here if you have had any issue related to the Swype beta, and explain what you have tried to fix it.
THanks!

zimphishmonger said:
Hello All,
I am attempting to work with Swype support, as I keep getting stuck in the DRM with the beta, which disables the product and pops up "used on another device, limited functionality", etc.
They have said they have tested it throughly, and have been "unable" to recreate the issue.
I would like to show them how many people are experiencing this issue, and have simply abandoned the beta, and have gone back to the WORKING leaked prerelease.
Please post here if you have had any issue related to the Swype beta, and explain what you have tried to fix it.
THanks!
Click to expand...
Click to collapse
I don't know what the cause is but I do know how to fix it. Simply long press on any text input box to bring up the "text input" option and select a different keyboard. Once that is done, do it again only this time select Swype. Bingo, back in action.

ItsDon said:
I don't know what the cause is but I do know how to fix it. Simply long press on any text input box to bring up the "text input" option and select a different keyboard. Once that is done, do it again only this time select Swype. Bingo, back in action.
Click to expand...
Click to collapse
Doesnt work for me, and I've been working with support and tried EVERYTHING (uninstall\reinstall, re-register, all the suggested fixes, etc)

I signed up for the beta, downloaded the file and installed it. I could swype all day and nothing appeared in the text box. Installed one of the previous unreleased versions and it worked fine, uninstalled and tried the beta again with same failure mode. Swype doesn't make it easy to comply with their requests to use approved software.

Both Swype support and myself have no idea why, but we were finally able to get Swype up and running on my phone.
Huge thanks for Brian from Swype support for his help, and I recommend anyone having issue to contact their support to see if you can get the issue resolved.
The app has a somewhat complicated (encrypted) registration process, and somehow that was not completing successfully, so def let support know if you are running into similar issues

This happened to me too. I gather it happens every time I install a different ROM, I need to contact Swype to get my Beta account re-authed.
Stuff that, I can't be bothered, I'll just wait until the paid version comes out.

Thought I'd give it another try and still get the "Limited Functionality..."...As usual with restricted access, DRM, etc, it is the ones who try and follow the rules who lose...the pirates will always find a way. Back to the leaked version for me, I guess, though I do think the HTC IME keyboard is still faster and more accurate.

I also get the "limited functionality" message, but only occasionally.
I haven't tested this hypothesis, but seems like it only does this to me when I am at home--and when I'm at home, I'm usually on wifi.
Maybe there's some kind of DRM that didn't take into account that people may occasionally switch from 3G to wifi connections.
If I had more time I'd try messing with it a bit, but I'm just headed to sleep.

There's probably a call home check on first application start up. When you wipe or switch ROMs, that will be cleared, but their servers already have the product registered.
Try backing up the app-data for Swype in between wipes/ROM updates.

I got the "limited functionality" message every time, no ROM updates between download and install. I even reinstalled the installer, redownloaded, etc and it just doesn't work. Glad it didn't work, because it convinced me to go back to HTC IME which is faster and more accurate for me.

http://www.mediafire.com/download.php?toniw2xejzz
its from the other swype thread and this worked for me.
hope for the rest also

well, after some time testing and thinking about this issue i found out whats the cause of it, it happens after rebooting the phone, the reason for this is that rooted roms zip align newly installed apps which changes a lot of things in the file, and i think that the registration process requires the main apk to remain unchanged, maybe someone can contact swype developers and tell them about this and hope that they can find a solution for it.

I have confirmed with a swype tech that there is a registration\call back home immediately following the install of the apk. If successful it will have a quick spinner stating "reristering swype" and the ask you to "enable swype".
I, unfortunately, seem to have major issues getting it to actually call back home, where it states "Swype has already been installed. please uninstall and try again" (I had previously uninstalled it).
In the end, had to revert back to the leaked versions

m_kayali said:
well, after some time testing and thinking about this issue i found out whats the cause of it, it happens after rebooting the phone, the reason for this is that rooted roms zip align newly installed apps which changes a lot of things in the file, and i think that the registration process requires the main apk to remain unchanged, maybe someone can contact swype developers and tell them about this and hope that they can find a solution for it.
Click to expand...
Click to collapse
Ive tried MULTIPLE times to uninstall and reinstall swype w/o rebooting, so I think it wouldn't have a chance to zipalign until the next reboot.

Kind of sad that Swype hasn't gotten back to me yet

Somehow, I am using the Beta version I downloaded myself. I was trying out Super D for a week which is when the Beta was open, later I went back to Dwang and Swype broke when using the Beta installer but I got it working using AppMonster. Here's the steps I followed over that time:
- Wipe phone and install Super D
- Install AppMonster from Market
- Sign up for Swype Beta
- Download SwypeInstaller and install Swype Keyboard
- Perform backup with AppMonster
- Wipe phone and install Dwang
- Download SwypeInstaller and install Swype Keyboard
At this point I got the "Limited Functionality" message
- Wipe phone and install Dwang again
- Install AppMonster from Market
- Restore backup of Swype with AppMonster
Now I can go into Settings and enable Swype in the usual way. I have been using it without a problem for a couple of weeks now.

What solved it for me
I had Swype installed and working on a G1 with Cyanogen latest but after an uninstall it stopped working for me with the same error messages as described here in this forum.
What solved it for me is not pushing the done button on the touch screen after the package install but pushing the back key on the phone. This got me in the registering Swype screen after which the swype installer crashed. Swype is fully working however using these steps.

just go back to installer , log in and reinstall. Everytime i flashed a new rom i did this. I found out u can do this 10 times, before they cut u off. Obviously they know whats up?!
obviously i like the real beat with vibration option and more stable. im using now the final pre release that was made available in a couple posts above mine. no vibration, but it works. this keyboard is fantastic!

Sprint hero sends but won't receive texts?

I have a rooted sprint hero running aosp mod (latest stable, not gingerbread - don't remember the version number). Up until Sunday everything was working fine. Sunday evening I noticed that I hadn't gotten any texts all day (highly unusual). Started to text my fiancée, didn't recieve a response. Called her a couple hours later, she said she'd recieved them and replied. I figured it was a sprint issue and would pass by the next day. Next day, still nothing. Stood next to a friend of mine, had him text me, nothing. Sent him a text and he received it almost instantly. As of today I still can't recieve texts, though everything else works just fine. Is this a simple software issue on my end that can be fixed by reflashing my rom? Or is it something more serious that I need to see a sprinnt Rep for? Any help will be greatly appreciated.
Sent from my HERO200 using XDA App

I saw a guy have this issue with cyanogenmod. He ended up flashing a different rom and all his texts came through at once then. He was using the nightly releases, so I think he just waited until the next nightly came out. You might should just reflash and see if that helps.

This is a common issue. Usually it is due to deleting the stock messaging app because you have handcent or chomp, but those apps pull the info from the stock sms app, so if you deleted it, reinstall it. The other cause is just a known bug in froyo, and though I have never had the issue, many many others have been able to fix it by going into recovery, nandroiding your current setup, wipe EVERYTHING, flash a sense rom, go into settings and update your profile and PRL, then open texts up (you should get a bunch), then going back into recovery, wipe everything again, and restore your nand. Hope this fixes it, good luck.

Sounds good, I'll give it a shot when I get off work. Does it matter what sense rom I flash? More specifically, can I just use an ruu from HTC.com or will I lose my root?
Sent from my HERO200 using XDA App

mushroom_cult said:
Sounds good, I'll give it a shot when I get off work. Does it matter what sense rom I flash? More specifically, can I just use an ruu from HTC.com or will I lose my root?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
RUU takes longer. also, dpending on how you rooted you will probably lose root. just run ANY sense based rom (custom too), fresh,NFX,liquid, whatever, it'll only take like 5-10 minutes. Also, just a hint, make a nand of the sense rom before you go back to your current one, that way you can update your profile/PRL whenever you want. I keep a sense NFX rom in my nand folder for just that.

Or you can wait till I release an updated dualboot script and have both easily accessible. Should be released this week.
Oh, and like some others said, its a problem with froyo and some phones. You might look in the froyo sense thread and try the fix listed in the first post.
Sent from my HERO200 using XDA App

unCoRrUpTeD said:
Or you can wait till I release an updated dualboot script and have both easily accessible. Should be released this week.
Oh, and like some others said, its a problem with froyo and some phones. You might look in the froyo sense thread and try the fix listed in the first post.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Can you tell us the specifics of what it will do?

I'll post a link later. I'm still adding to it, but plan on releasing it Friday.
Sent from my HERO200 using XDA App

unCoRrUpTeD dualboot <----Here is the link to the thread that will host everything and my thread in the Hero CDMA developement will be redirected to here also.

il Duce said:
This is a common issue. Usually it is due to deleting the stock messaging app because you have handcent or chomp, but those apps pull the info from the stock sms app, so if you deleted it, reinstall it. The other cause is just a known bug in froyo, and though I have never had the issue, many many others have been able to fix it by going into recovery, nandroiding your current setup, wipe EVERYTHING, flash a sense rom, go into settings and update your profile and PRL, then open texts up (you should get a bunch), then going back into recovery, wipe everything again, and restore your nand. Hope this fixes it, good luck.
Click to expand...
Click to collapse
You're awesome. Followed your advice, worked perfectly.
However, I'm now having a separate issue (I assume). All physical keys work fine, with the exception of my home key which does absolutely nothing once the phone boots. Is this a related issue? Did I screw up somewhere along the line?

mushroom_cult said:
You're awesome. Followed your advice, worked perfectly.
However, I'm now having a separate issue (I assume). All physical keys work fine, with the exception of my home key which does absolutely nothing once the phone boots. Is this a related issue? Did I screw up somewhere along the line?
Click to expand...
Click to collapse
I have heard of this as well. Can't remember the fix, but it sounds rom related. The home key action is in /system/usr/keylayout/heroc-keypad.kl you can also check there? You could try to re-restore the nand again - wipe ALL first. Also, I know most launchers have home key options, make sure those settings look normal. Also maybe go into your launcher app in settings/apps/manage apps and clear the defaults for it, then see if home does anything. IF that doesn't work search for member "appleflap" on xda, he made a hardkey remapper that you can fix/change the function of the home key.

Reflashed the current nand to no avail. Flashed a clean install of aosp, works fine. I can deal with the loss of my settings, I suppose.
Thanks for all of your help, bud.
Sent from my HERO200 using XDA App

I am actually having a similar issue, but I am periodically not able to send texts. Receive just fine, but some texts fail over and over.
I am running CM 6.1 stable, and using the default text app. Anyone had this issue?
Sorry about the bump, but I did not feel it necessary to create a new thread after I found this one.
Edit: I totally also recognize this could be something to do with the sprint network as well

[Q] Issue with status and google voice w/phiremod

Hey folks,
I just flashed over the latest phiremod and I'm having a couple of small issues. 1: Whenever I go into settings > about phone and hit "status," it force closes on me before I can even see any info (like batt. status, level etc). Anyone experience anything similar and if so, found any workaround?
2: I downloaded and installed the newest version of Google Voice from the market but can't set it up. During set up, after I provide the number associated with it the next step attempts to set up voicemail (and obviously can't) so I just press the option to "skip" it, but whenever I do so the set up screen and the buttons go grey and just stay that way. Anyone know of any workarounds?
Thanks for any help!

Hope it's alright to bump this. Again, if anyone has any idea on a fix, I'd really appreciate it. (Of course, if I missed a thread or two about these same issues, feel free to throw in a link.)
Thanks!

Android 6.0 Marshmallow Apps Blocking MMS

I should probably post this somewhere else because I know it's an issue for more than the Nexus 6, but ever since I updated to 6.0 a few weeks ago I keep having issues sending and receiving MMS. It probably took me a week or more to notice the first time, but after a lot of pulling my hair out for almost a week I figure out it was Ad Away. I uninstalled and all was well. I know I could have messed with the ports in the APN profiles but I didn't want to be bothered.
Last week ES File Explorer updated with their terrible update and aside from the annoying new features, once again MMS stopped working. This was a little easier to pinpoint and once I uninstalled my MMS started working again.
Today I'm having trouble with MMS again. I started searching on the topic again, this time focused on Marshmallow and found a lot of people pointing fingers at Pushbullet. Also found people saying that Chrome was not set as the default browser and that assigning it fixed the problem for them. Luckily that was the case for me and I still have pushbullet (phew).
However, I feel like I'm just scratching the surface on this issue. What's up with Marshmallow that apps keep breaking MMS so easily? Is the Chrome default setting the underlying culprit here? I didn't check it the first two times but I'm wondering if I can reinstall other apps now haha. Obviously it'll be the first thing I check the next time this happens -_- but I'd like to understand what's happening better.
So do any of you smarter-than-me people understand this?
Update: I wasn't imagining things haha.
http://www.androidpolice.com/2015/1...s-the-annoying-failed-mms-bug-in-marshmallow/

CLAWHAMM3R said:
I should probably post this somewhere else because I know it's an issue for more than the Nexus 6, but ever since I updated to 6.0 a few weeks ago I keep having issues sending and receiving MMS. It probably took me a week or more to notice the first time, but after a lot of pulling my hair out for almost a week I figure out it was Ad Away. I uninstalled and all was well. I know I could have messed with the ports in the APN profiles but I didn't want to be bothered.
Last week ES File Explorer updated with their terrible update and aside from the annoying new features, once again MMS stopped working. This was a little easier to pinpoint and once I uninstalled my MMS started working again.
Today I'm having trouble with MMS again. I started searching on the topic again, this time focused on Marshmallow and found a lot of people pointing fingers at Pushbullet. Also found people saying that Chrome was not set as the default browser and that assigning it fixed the problem for them. Luckily that was the case for me and I still have pushbullet (phew).
However, I feel like I'm just scratching the surface on this issue. What's up with Marshmallow that apps keep breaking MMS so easily? Is the Chrome default setting the underlying culprit here? I didn't check it the first two times but I'm wondering if I can reinstall other apps now haha. Obviously it'll be the first thing I check the next time this happens -_- but I'd like to understand what's happening better.
So do any of you smarter-than-me people understand this?
Click to expand...
Click to collapse
No0 the chrome issue is not really a big deal. I dont have it set as mine and mms works fine. The pushbullet thing is a known issue. Are you using a 3rd party sms app?

I was having the same issue, nothing exoctic installed, using stock messenger. I played with the apn settings to no avail. I ended up installing chomper and haven't had a problem since

none
[/COLOR]
CLAWHAMM3R said:
I should probably post this somewhere else because I know it's an issue for more than the Nexus 6, but ever since I updated to 6.0 a few weeks ago I keep having issues sending and receiving MMS. It probably took me a week or more to notice the first time, but after a lot of pulling my hair out for almost a week I figure out it was Ad Away. I uninstalled and all was well. I know I could have messed with the ports in the APN profiles but I didn't want to be bothered.
Last week ES File Explorer updated with their terrible update and aside from the annoying new features, once again MMS stopped working. This was a little easier to pinpoint and once I uninstalled my MMS started working again.
Today I'm having trouble with MMS again. I started searching on the topic again, this time focused on Marshmallow and found a lot of people pointing fingers at Pushbullet. Also found people saying that Chrome was not set as the default browser and that assigning it fixed the problem for them. Luckily that was the case for me and I still have pushbullet (phew).
However, I feel like I'm just scratching the surface on this issue. What's up with Marshmallow that apps keep breaking MMS so easily? Is the Chrome default setting the underlying culprit here? I didn't check it the first two times but I'm wondering if I can reinstall other apps now haha. Obviously it'll be the first thing I check the next time this happens -_- but I'd like to understand what's happening better.
So do any of you smarter-than-me people understand this?
Click to expand...
Click to collapse
Are you using the stock message app? not that you should have to put a different messaging app on your phone to fix the issue, but purely from a troubleshooting perspective have you tried that? Personally I didn't care for the stock app so when the Stagefright terror came about I switched to Textra and have been there ever since. It really is an awesome MMS app, maybe give that a go and see what happens, and once you use Textra, I doubt you will want the stock app.

zelendel said:
No0 the chrome issue is not really a big deal. I dont have it set as mine and mms works fine. The pushbullet thing is a known issue. Are you using a 3rd party sms app?
Click to expand...
Click to collapse
Was just curious if something was clearing Chrome and causing this to happen, and if maybe I had known about this and tried it the last two times I wouldn't have had to uninstall anything.
Gage_Hero said:
I was having the same issue, nothing exoctic installed, using stock messenger. I played with the apn settings to no avail. I ended up installing chomper and haven't had a problem since
Click to expand...
Click to collapse
USMC retired said:
[/COLOR]
Are you using the stock message app? not that you should have to put a different messaging app on your phone to fix the issue, but purely from a troubleshooting perspective have you tried that? Personally I didn't care for the stock app so when the Stagefright terror came about I switched to Textra and have been there ever since. It really is an awesome MMS app, maybe give that a go and see what happens, and once you use Textra, I doubt you will want the stock app.
Click to expand...
Click to collapse
Using the stock Google Messenger app. I tried using Hangouts as the default SMS app but it happened there too. I hate SMS/MMS so I really want to avoid downloading any additional apps haha. I usually try to force people into using an instant messenger but you know how people can be. It's just annoying because I usually don't even get a notification that I'm missing messages. I just open conversation and it says "tap to download" or "downloading..."
I'm working fine now so maybe the next time it breaks and Chrome as the default browser isn't the fix it I will explore some third party apps, it just seems like this is a "thing" with Marshmallow.

http://www.androidpolice.com/2015/1...s-the-annoying-failed-mms-bug-in-marshmallow/

I had the same issue. Got my nexus 6, before even setting it up, I rooted and installed marshmallow pure nexus. I'm on T-Mobile. I had 3 apn's under settings. The fast-tmobile had mmsc blank. The 3rd apn had T-Mobile mmsc filled. I copied that, pasted it into the fast-tmobile apn, clicked save, then deleted the other 2 apn's. I use hangouts, and since doing that, I've had zero issues at all. If I change roms, its the first thing I do. I'm more inclined to believe it's in your apn. Many people have had the same issue. I went back to 5.1.1 and took the ota. Mms was broken and I had to apply the same fix. Still on the stock ota, and all has been well. Good luck
Sent from my Nexus 6 using XDA Free mobile app