Last night I was checking out Cyanogen's web site and I came across this:
Bluetooth Voice Commands Missing in CM6?
Hello,
One of the newer features that I liked so far in CM-6 was the ability to long press my bluetooth headset action button which resulted in a voice telling me to say a command. This was much better than the original phone voice dialer, which requires manual intervention to pick a number from its list of guesses after you speak, and which offers no voice prompt to let you know when it's ready.
Well, as of upgrading to CM-6.0 from the 8-25 nightly, the bluetooth/headset dialer is gone and when I long press my bluetooth headset button It's back to the old phone voice dialer which requires manual intervention to place a call and offers no voice prompt. How do I get the bluetooth dialer back?
I have attached the 09SEP-VoiceDialer.apk from CM-6 release for easy downloading.
***Instructions- Download the file into your root of your SD card, using Root Explorer remove the old VoiceDialer.apk and install the new 09SEP-VoiceDialer.apk
The OLD VoiceDialer.apk can be found under /system/app
Mine is working great!
Any questions, PM me....
Enjoy!
my bluetooth headset can now operate the voice commands, however, after a command is given, Voice Dialer FCs.
KF34
gohamstergo said:
my bluetooth headset can now operate the voice commands, however, after a command is given, Voice Dialer FCs.
KF34
Click to expand...
Click to collapse
Did you remove the old VoiceDialer.apk?
Also, don't forget to change the permissions on the 09SEP-VoiceDialer.apk after yoo move it to /system/app.
This is working great for me, back to the way it was before the update!
Sent from my FroyoEris using XDA App
so as far as the instructions:
***Instructions- Download the file into your root of your SD card, using Root Explorer remove the old VoiceDialer.apk and install the new 09SEP-VoiceDialer.apk
is install the new file is just copying it then pasting it into the system/app folder using root explorer, longpress on app and change permissions to allow all. then reboot.
EDIT: apparently yes, my bt headset works perfectly with voice dialer now. thank you.
This is great -- restores the BT voice dialing functionality that should have been stock in the Eris from the start
Is the source for this APK available? I wonder if it would be possible to modify to add an optional "confirmation" step:
User: "Call Jim Somename"
Phone: "Calling Jeff Someothername, is that correct?"
User: "No"
Could certainly be fancier, like presenting several options, but the above would be sufficient to prevent misdialing people you don't mean to call in other area codes, etc. That's my main hesitation to use it right now; my wife's name, in particular, seems to mismatch to other names often.
I haven't done much Android development yet, but I'd be interested in poking at this code.
jmastron said:
This is great -- restores the BT voice dialing functionality that should have been stock in the Eris from the start
Is the source for this APK available? I wonder if it would be possible to modify to add an optional "confirmation" step:
User: "Call Jim Somename"
Phone: "Calling Jeff Someothername, is that correct?"
User: "No"
Could certainly be fancier, like presenting several options, but the above would be sufficient to prevent misdialing people you don't mean to call in other area codes, etc. That's my main hesitation to use it right now; my wife's name, in particular, seems to mismatch to other names often.
I haven't done much Android development yet, but I'd be interested in poking at this code.
Click to expand...
Click to collapse
I do not know but I can give you a link to Cyanogen's post if you would like....
http://forum.cyanogenmod.com/topic/6497-bt-voice-dialing/page__p__57811__hl__bluetooth__fromsearch__1#entry57811
I remove the old voicedialer. I copied over to system/app change the perms and reboot. when long pressing the bluetooth the dialer comes up but never prompts. I tried renaming the file. I tried just an install. that worked once but FC verytime after.
What am i doing wrong
Thanks for this
I can't believe that Google has worse technology than MS on this! MS Voice Command is far superior.
I tried vlingo with mixed results.
Will try this.
Just installed on my Aria running Liberated 2.2 and it works great!
BTW, I couldn't for the life of me delete the old VoiceDialer.apk using a file explorer, so I just took a shot and installed this Voice Dialer, so no real need as far as I can tell to go through the hassles of the instructions above.
Many thanks.
I tried.this but I keep getting a parsing error ???? I'm a noob have no clue what that means..lol
Sent from my Eris using XDA App
I realize that this is a bit of a dead post, but do you think this apk would work on a Samsung Captivate? I'm currently running with Perception 10.3 and Speedmod kernel, but for some reason the BT Voice Dialer has decided to stop working and is continually stuck at Starting Up.
I'm trying to get this to work on my Aria running FR0008 but no dice. Even using Root Explorer I simply cannot get either the original Dialer.apk deleted or the replacement 09SEPDialer.apk installed.
What am I doing wrong? I REALLY want the proper Bluetooth dialer in this ROM as I use a headset often and at the moment I prefer it to the Cyanogen ROMS.
woodbane said:
I'm trying to get this to work on my Aria running FR0008 but no dice. Even using Root Explorer I simply cannot get either the original Dialer.apk deleted or the replacement 09SEPDialer.apk installed.
What am I doing wrong? I REALLY want the proper Bluetooth dialer in this ROM as I use a headset often and at the moment I prefer it to the Cyanogen ROMS.
Click to expand...
Click to collapse
Have you tried this? Download the 09Sep-VoiceDialer.apk to your computer. Rename it VoiceDialer.apk and place it in your tools directory of SDK. Connect your phone to PC. Open a command prompt window and navigate it to your tools directory of SDK. Type adb remount. Then type adb push VoiceDialer.apk /system/app. Then adb reboot. Be certain to take not to the caps in the file name as well so it will overwrite the one that's already in place on your phone. Hope this helps
CondemnedSoul said:
Have you tried this? Download the 09Sep-VoiceDialer.apk to your computer. Rename it VoiceDialer.apk and place it in your tools directory of SDK. Connect your phone to PC. Open a command prompt window and navigate it to your tools directory of SDK. Type adb remount. Then type adb push VoiceDialer.apk /system/app. Then adb reboot. Be certain to take not to the caps in the file name as well so it will overwrite the one that's already in place on your phone. Hope this helps
Click to expand...
Click to collapse
That sounds very helpful, only problem is I have no idea about SDK and ADB. Is there a really abbreviated way of getting me up and running with this?
woodbane said:
That sounds very helpful, only problem is I have no idea about SDK and ADB. Is there a really abbreviated way of getting me up and running with this?
Click to expand...
Click to collapse
Try here http://developer.android.com/sdk/index.html
There's instructions for installation and the downloads. Everything you should need
CondemnedSoul said:
Try here http://developer.android.com/sdk/index.html
There's instructions for installation and the downloads. Everything you should need
Click to expand...
Click to collapse
Awesome, I'll try giving that a whirl later this evening. Thanks for the pointer.
So, I gotta be honest, I just simply do not have the technical know how to get this working. I've downloaded and installed all relevant files but can't even seem to get the phone connected.
Here's what I'd love to be able to do, simply replace the VoiceDialer.apk in the Aria FR008 ROM - which does not support Bluetooth voice dialing with this one that apparently does.
I have tried unzipping the FR008 ROM and replacing the file and rezipping. When I go to install it from card in recovery mode it immediatly crashes. I'm seeing that the FR008 zip is "signed" and guess that I'm missing doing something important here, resigning either the whole ROM or just the file?
Can anyone please help me out here as I'm really struggling with this.
woodbane said:
So, I gotta be honest, I just simply do not have the technical know how to get this working. I've downloaded and installed all relevant files but can't even seem to get the phone connected.
Here's what I'd love to be able to do, simply replace the VoiceDialer.apk in the Aria FR008 ROM - which does not support Bluetooth voice dialing with this one that apparently does.
I have tried unzipping the FR008 ROM and replacing the file and rezipping. When I go to install it from card in recovery mode it immediatly crashes. I'm seeing that the FR008 zip is "signed" and guess that I'm missing doing something important here, resigning either the whole ROM or just the file?
Can anyone please help me out here as I'm really struggling with this.
Click to expand...
Click to collapse
Yeah... if you unzip it you will need to sign it when you zip it in order to flash it. Try opening to rom with 7zip or winrar and just drag and drop the new one into the zip to replace the old one. Don't unzip it.
Sent from my Blackened Ginger using XDA App
Related
Greetings. Been haunting this place for awhile, happy to finally have root.
After the phone is rooted the last step is something that sweeps up a bunch of SE's stock apps that most people don't want. What about us who actually liked a few of them, though?
I would have liked to keep the app called "TrackID," and am wondering if there's any way to get it back? I can't really find like a repository for the base APKs (I might want the Mixi plugin for Timescape back in the future, as well).
Can someone rip these out somehow for individual installing?
Here it is:
http://rapidshare.com/files/403753839/trackid.apk.html
Just install the apk.
Its works for me.
Nice threat, nice anwser.
It works fine with me too.
Thanks!
Preventing the rooting process from removing apps
Hello, You could just enter the step4 folder and open the cleanup.sh file in notepad or similar.
Remove the line saying rm *packagename here*. Then your app will only be copied to your SD, but it will also remain on the phone.
track id request
i couldnt download the package, the link no longer works :-(
Could someone uóad it again to another server? Because its a common problem and will br of much help thanks
http://balsat.hopto.org/builds/seX10-system/index.php?dir=..%2FseX10-system%2Fdir%2Fsystem%2Fapp%2F
ok... but now...
I have the app already installed, but now evertime it tries to connect it says "authentication error".... help?
I gave up and rooted the phone again, i went from steps 1 to 3 with no problems, using track id everytime to make sure it worked, and it did, I even used the cleanup script and it was there working very well...
So, I used steps 4 and 5 (for the X10a) But now it wont work... it says "authentication error".... what gives?
Sorry for my english, I´m from mexico...
Everything on my phone is working fine...
For TrackID I can only say that it was probably a rights issue.
Use chmod or Root Explorer to set the rights(644).
For step 4 and 5 i cant help,i have only a 3 step X10i ,sorry.
But dont give up, i think u find the help here on XDA.
So, went out and picked up a Mini Pro for the misses.
Well, off the bat I went crazy cause I couldn't find "Market" and well...after searching online, guess this damn region doesn't support the Market. How wonderful is that, so downloaded stuff online through slideme. Which really still sucks.
Then when I downloaded things to my laptop and wanted to bluetooth them over, I couldn't. Then when I wanted to send ringtones from my phone to the mini pro, I couldn't. So I searched, and wouldn't you know it. I gotta download a program, so I downloaded bluetooth explorer and then it prompted me that I gotta root this SOB to be able to send files through bluetooth? Did I just buy an iPhone or what?!
So I plugged in the phone through USB. And we copied over the APK. and I downloaded a file explorer, so I could get to the damn APK (really no file explorer included, or clearly apparent?). And when we launched the file (MSN), we found we couldn't send files, images, or anything other than text. Are you kidding me?
With all these limitations, how is Android so popular?
Are there any possible solutions without having to root this bastard? (aside from MSN). I just bought this thing and don't wanna void warranty so damn early so I could make it something PRACTICAL like every other phone.
I'm guessing you're used to nokia's and the like. I must say i've found bluetooth file transfer a little hit and miss on android, but you need an app called bluetooth file transfer but it's on the market i'm afraid. Where are you then? You can get the market app from these forums and an enabler for regions not supported so you may need to do some digging.
Sent from my E10i using XDA App
Not used to Nokia's. Used to WinMo and running Android Froyo on my Topaz.
Could not find the market standalone app for the life of me. And the phone is from Saudi Arabia, and I can't justify rooting it just yet.
@bmzloum
Hi! I feel your pain. Android Marketplace is not supported in my part of the world too. I am looking for alternate ways to get apps into my phone.
You mentioned that you had to download a separate File Manager to get to the .apk files. Can you tell me which app you are using?
Also how did you manage to install the File Manager in the first place if you could not get to the .apk files?
Do you copy the .apk files to your MicroSD card? Do you any other advice to make installation easier if we download the Apps to our computer then then try to install them to our phone?
Thanks in advance for any help.
Cheers and good luck with your new phone.
Appbrain App Market and Apktor are viable alternatives for getting apps on your phone, the latter you'll need to find public repositories for. Sorry can't post links cause of restrictions on a new account, but google knows all.
drussthelegend said:
You mentioned that you had to download a separate File Manager to get to the .apk files. Can you tell me which app you are using?
Click to expand...
Click to collapse
Hey, found
Code:
http://slideme.org/
which let me download with the barcode, and then I installed the sites app manager directly on there. There are a ton of file managers, I downloaded two, I forget which. But the two most popular ones. Both worked, but only one handled ZIP files. I don't have the phone beside me, so can't recall...
I found the Market standalone apk, but it crashed everytime I clicked on "Download" so I gave up on it.
I'm gonna try those suggestions posted up and see if they have a few new nice apps on there.
I had the exact same issue as others above. My solution was to use the debranded UK Firmware, root the phone and then use the Bluetooth File Manager.
bmazloum: My phone also came from the UAE side and didn't have the Market. I used Omnius to flash the firmware. A friend of mine on the otherhand paid the local Sony Service Centre to flash and debrand the ROM. Maybe this might help
Guys you don't have to move the apk file over to the phone in order to install it btw... get Adb from the Android SDK and then place the apk file in the same folder as adb.
And then from command prompt, navigate to the folder with adb and your apk and type "adb install example.apk".
Make sure you have USB Debugging (Applications -> Development) enabled and that's it.
Works nicely on a Mini. Not sure about the Pro to be honest.
Google Talk is an instant messaging, audio and video chat service from Google, which is being designed for users to communicate in real time with other users who also use Google Talk. To complement Google Talk on desktop computer, Google has recently expanded Google Talk to Android phones with video and voice chat. With the new added service to Android phone, the users can now make a video or voice chat with their friends, family and colleagues who also use Google Talk on Android devices or on desktop PC.
Key features of the Google Talk for Android includes:
Able to make calls over 3G or 4G data network (if your carrier supports it) or over Wi-Fi.
Simply touch the video or voice chat button to connect with the friends or family members who are in the Google Talk friends list.
Text-chats will be overlaid on the phone screen while you are on video with others.
The video will automatically pauses and audio will keep going when you need to check something else from the Home screen or apps.
Google Talk with video and voice chat has already started to delivered to Google Nexus S devices as part of the Android 2.3.4 over-the-air update. Other Android devices will have to wait until the phone manufacturers such as HTC, Samsung, Motorola, LG and etc to start offering upgrade to Android 2.3.4 for their respective phones in order to get Google Talk with video and voice call feature.
If you can’t wait for the Google Talk with video chat support to come to your phone, which may take weeks or months to arrive, a hacker named britso has managed to extract Google Talk 1.3 app with video plus voice call support from Google Nexus S Android 2.3.4 update, hack the SigninActivity.smali to comment out a line so that the app works on other devices. The app is then re-compiled and pushed as the APK file for installing into other Android mobile phones running Android 2.3 or above.
Listed below are several ways on how to instal lGoogle Talk with voice and video chat support onto your Android smartphone. Note that the hack only works on rooted Android phone.
The download links of Google Talk apk is available from xda-developers.com (registration required).
Method 1: Via ADB
1.Download either Talk_with AV.zip or Talk_with_AV_no_wifi.zip.
2.Connect the Adnroid phone to PC and run following commands on ADB console:adb remount
adb shell mv /system/app/Talk.apk /system/app/Talk.apk1
adb uninstall com.google.android.talk
adb push libtalk_jni.so /system/lib/
adb push Talk2.apk /system/app
3.Run Talk and press on your own name where you can change your own status and tick the Allow video and voice chats to enable the feature.
Method 2: Using Root Explorer
1.Download and extract Talk_with AV.zip to SC card.
2.Open Root Explorer and navigate to extracted files on SDcard.
3.Copy talk2.apk and go to /system/app.
4.Press Mount R/W at the top right and then press Paste on the bottom left.
5.Now you have both talk.apk and talk2.apk.
6.Rename Talk.apk to Talk.apk1.
7.Select and hold the other Talk2.apk and press Permissions and select:User: Read Write
Group: Read
Others: Read
And press Ok.
8.Now press and hold on Talk2.apk and press Rename.
9.And rename Talk2.apk to Talk.apk.
10.Go back to extracted files SDcard and copy libtalk_jni.so.
11.Navigate to system/lib.
12.Press Mount R/W at the top right and then press Paste on the bottom left.
13.Press and hold on libtalk_jni.so and select Permissions, and change the permissions to:User: Read Write
Group: Read
Others: Read
14.Reboot the device.
15.Open Talk and press on your own name where you can change your own status and tick the Allow video and voice chats to enable the feature.
Eh? Confusion....
nierainbow said:
Listed below are several ways on how to instal lGoogle Talk with voice and video chat support onto your Android smartphone. Note that the hack only works on rooted Android phone.
The download links of Google Talk apk is available from xda-developers.com (registration required).
Click to expand...
Click to collapse
Thank you for your attempt to provide useful information, however this is really confusing.
Here are some helpful hints for future posts:
1. There is no download link in this thread or reference to the original post. You should try to fix it. I think this is the link you are referring to:
http://forum.xda-developers.com/showthread.php?t=1056793
2. We are on xda-developers as such why do you need to include the line registration is required. Don't just copy and paste information you found somewhere else, we are getting no where.
3. Include something useful or insightful such as "Hey here's another method and the link is below!" Something like that.
(Thanks BluechipJ!)
4. Find out if this is the correct forum/category to post in. Ask yourself the following questions: Am I developing something for the ARC? Am I asking a question? Is this theme or an app I am discussing? Is this general information?
5. Don't forget to use the search function and think before you post.
Hopefully this helps.
Whats the point of even posting it here. the arc doesn't have a front camera.
tsangwc said:
Whats the point of even posting it here. the arc doesn't have a front camera.
Click to expand...
Click to collapse
use the rear cam?
http://forum.xda-developers.com/showthread.php?t=1075494
here you find simplest way: an apk that does everything for you
also runs on 2.3.2
(& better than on htc devices since there every video is rotated by 90° ^^)
still only rear cam.. of course
kistigun said:
use the rear cam?
Click to expand...
Click to collapse
To use the rear cam to do voice chat, you have to either let people see you or you see them.
Sit before a mirror and use rear cam, you can see them, they can see you...
you have gingerbred 2.3.4 ?
While copying the .so file to /system/lib I face two problems :
1) i don't get mount r/w instead i get mount r/o.
2) if i tap mount r/o and paste the file it says not enough space, even if i don't tap mount r/o and then paste it, it says the same thing.
I have like 916KB free and 276MB used.
Is the folder dynamically expanding?
Or i have used a lot of space?
No app showing
So I installed with the root explorer method it all went fine. Gmail and market still working. But I don't have a "talk" app to use now.
not2cocky said:
So I installed with the root explorer method it all went fine. Gmail and market still working. But I don't have a "talk" app to use now.
Click to expand...
Click to collapse
Try this method.
http://android.modaco.com/topic/339390-r1-12-may-google-video-talk-installer/
WORK
Work in my xperia pro cyanogenmod 7.2 rc1 fxp 115
Google talk voice/video works for Samsung Galaxy I9003
sopdogg said:
Thank you for your attempt to provide useful information, however this is really confusing.
Here are some helpful hints for future posts:
1. There is no download link in this thread or reference to the original post. You should try to fix it. I think this is the link you are referring to:
http://forum.xda-developers.com/showthread.php?t=1056793
2. We are on xda-developers as such why do you need to include the line registration is required. Don't just copy and paste information you found somewhere else, we are getting no where.
3. Include something useful or insightful such as "Hey here's another method and the link is below!" Something like that.
(Thanks BluechipJ!)
4. Find out if this is the correct forum/category to post in. Ask yourself the following questions: Am I developing something for the ARC? Am I asking a question? Is this theme or an app I am discussing? Is this general information?
5. Don't forget to use the search function and think before you post.
Hopefully this helps.
Click to expand...
Click to collapse
This is method works for my Samsung Galaxy SL I9003 (ROOTED) mobile with Android 2.3.6. Some features I miss here are not able to choose front facing Camera, Video Chat status not visible for Others (but we can know who are having voice/video capability).
Anyhow works fine for me, Many thank to you!
Work in MK16 i and a CM7 RC
VERY THANKS
Enviado desde mi MK16a usando Tapatalk
do you have gtalk (can voic and video)for 2.3.7?
do you have gtalk (can voic and video)for 2.3.7?gtalk in my cm7.2 can only chat in text,not voic and video!thx
?????
where is the linke????????????
I recently rooted and unlocked my Atrix 4g and flashed to cm7, when I did I lost Nuance voice commands. I would like to get it back cause I use a bluetooth headset on my motorcycle. Nuance voice commands echoes back where it's at.
most all the other voice dialers either don't work or you have to see the screen.
I tried to install voice.nuance.recover-v1.zip but found out it doesn't work for cm7.
Any suggestions?
Any solution ?
Hi Jam van,
Did you found a solution ? I also miss Nuance on my CM7 Atrix (CM10 at the moment, for test)
I'm still lokking for a Free application that allow offline dialing with aural confirmation and of course in French
I've tested the google build-in, offline, voice control software, but it'd useless !! It even unable to understand 'appeler Maman' ('Call mum') which is a basic instruction
I miss a lot the basic WM6 voice-tag-based application; sometimes I'm thinking on switching back to my old WM6 HTC Diamond.
try this http://forum.xda-developers.com/showthread.php?t=1498604
Also, try this replacement to Nuance http://www.androidpolice.com/2012/0...-a-stellar-voice-recognition-app-for-android/
palmbeach05 said:
try this http://forum.xda-developers.com/showthread.php?t=1498604
Click to expand...
Click to collapse
I'm right now on the Alpha CM10 not sure VSuite vorking with Adnroid 4.x.
Secondly and main problem, it seems the proposed version is not working through BT (I was sure it was working on the original Motorla Firmware); and want voice dialing for my motorbike's BT helmet kit; so is need full BT support and auran confirmation because I can't look at the screen while riding :laugh:
palmbeach05 said:
Also, try this replacement to Nuance http://www.androidpolice.com/2012/0...-a-stellar-voice-recognition-app-for-android/
Click to expand...
Click to collapse
Dragon Go! has disepeared for Android, it has been replaced by Dragon Mobile Assistant; has for dragon Go!, it only work for english speaking people and I'm not convinced it's working Offline like the oroginal Nuance VSuite.
Thanks palmbeach for your 2 porpositions, I'm open to any other suggestion, because I miss that the feature alot. :crying:
Foo Bar said:
I'm right now on the Alpha CM10 not sure VSuite vorking with Adnroid 4.x.
Secondly and main problem, it seems the proposed version is not working through BT (I was sure it was working on the original Motorla Firmware); and want voice dialing for my motorbike's BT helmet kit; so is need full BT support and auran confirmation because I can't look at the screen while riding :laugh:
Dragon Go! has disepeared for Android, it has been replaced by Dragon Mobile Assistant; has for dragon Go!, it only work for english speaking people and I'm not convinced it's working Offline like the oroginal Nuance VSuite.
Thanks palmbeach for your 2 porpositions, I'm open to any other suggestion, because I miss that the feature alot. :crying:
Click to expand...
Click to collapse
no problem. i'm on atrix hd running 4.1.1 and VSuite is present and working. so yes, it does work on at least up to 4.1.1. The Droid X2 link was for CM7 and does solve the BT and echo issues.
I'm not aware of the change to Dragon Go!, its not an app that i normally use. i can see what i can dig up to replace this for non english speaking people. i also do not know how stable it is offline, its one of those things you or anybody for that matter would have to test out and see what happens.
jam van said:
I recently rooted and unlocked my Atrix 4g and flashed to cm7, when I did I lost Nuance voice commands. I would like to get it back cause I use a bluetooth headset on my motorcycle. Nuance voice commands echoes back where it's at.
most all the other voice dialers either don't work or you have to see the screen.
I tried to install voice.nuance.recover-v1.zip but found out it doesn't work for cm7.
Any suggestions?
Click to expand...
Click to collapse
Try this pack file in link bellow, using a ROOT device and a file manager (ex: ES File Explorer File Manager)
1. Download and unzip above file to your external or internal storage in a temp folder.
2. Copy VSuiteApp.apk file from "temp"/system/app in unzipped folder to /system/app folder on your device.
3. Copy "nuance" folder from "temp"/system/etc in unzipped folder to /system/etc folder on your device.
4. Copy "libvsuite_mot_vs45_embedded.so" file from "temp"/system/lib in unzipped folder to /system/lib folder on your device.
5. Copy "nuance" folder from "temp"/system/tts in unzipped folder to /system/tts folder on your device.
6. Fix permission on all copied files (individual or in folders copied over) to rw- r-- r--.
7. Reboot.
8. Update the "Voice Commands" (Vsuite 4.5 old version JBREL1-1.2.05 to 1.2.15) to version JBREL1-1.2.20 by Google play.
Since there's now an Xposed Framework Module available to do this same thing, that is the much better way to go than modifying your framework-res.apk directly.
Check that out here http://repo.xposed.info/module/de.makuser.nexussms
-Original post follows-
I got tired of seeing several threads about this topic so I figured I would post a "How to", which should work on all ROMs and versions around.
This procedure is actually fairly simple, and if you have basic Android and computer knowledge you can do this.
What Does This Do?
On mobile-enabled tablets like the N7 3G and the N7 LTE, the device itself is capable of sending & receiving MMS and SMS messages. Maybe you've read about how Google Hangouts got the ability to do this not too long ago. However, if you excitedly downloaded and installed the new version, you may be like "What the hell is this?!?" because by default you cannot see any SMS-related options. In Jellybean and KitKat, a device has to be "a phone" before the system thinks the device is able to send SMS and MMS messages. However, its fairly easy to change this particular property on your device so that it self-identifies as a "phone" and you get access to SMS.
Important: You actually have to have SMS service to use SMS service. Even though it boggles my mind, people have actually sometimes been confused by this particular mod, and have asked me if it somehow gives you SMS service. It does not, it only gives you access to the software functionality to send and receive SMS messages.
Even More Bolded Text!: there is one exception to this. If you are using CyanogenMod 10.2 (or 11 if they have ported Voice+ to it, not sure at this time), you can use this mod in conjunction with Google Voice and the Voice Plus app. Voice+ allows you to send & receive messgaes via the Google Voice service behind the scenes, but on the front end you can use the stock MMS.apk, or the Google Hangouts app to do this. This does not involve modifying Google Hangouts, its just sort of "bridging" Google Voice and the native SMS handling so that your Google Voice texts act like regular SMS messages. Voice+ is part of the CyanogenMod project and you can read more about it here. It's honestly pretty nice if you're a Google Voice user, since the regular Google Voice app kindof sucks.
This procedure involves modifying a boolean setting in your device's framework-res.apk file. That may sound like gibberish to you, but its still not hard to get this done.
What You'll Need
This guide is written for people who use Windows. All the utilities I'll talk about in this guide are for Windows. I'm sure its possible to do this on Mac & Linux, but the main utility I use to make this easy (FrameWork Flasher) is for Windows.
-An archive manager. I recommend 7-Zip, since it is free, open source, and can handle basically every archive format known to man.
-FrameWork Flasher. I updated this application to work with KitKat, but am not the original creator. You can download the updated version from MediaFire. FrameWork Flasher was created by XDA's own Wes Foster, and you can see his original post here.
-Some kind of text editor. I use NotePad++
-An Android device with a custom recovery installed on it. "Custom Recovery" means like ClockWork Mod, or TWRP. You need this to flash your modded file back onto your device.
Got all your stuff together? OK, on with the How Tos.
How To Do This
The first thing you'll need to do is get a copy of your current ROM's framework-res.apk file. There are a variety of ways to do this. If you're running a custom flashable ROM, like CyanogenMod, the simplest way to go is to just download your ROM's flashable ZIP file onto your computer and then open it up in 7-Zip. The file should be located inside the ZIP in the system\framework folder. Just extract that to your Desktop, or wherever you're going to keep the files you're working on.
If you're running a "stock" firmware, probably the easiest way to get your current framework-res.apk is to copy it from your current tablet. Note: this method should always work regardless what ROM you are running, I just find it easier to pull the files out of the downloaded ZIPs on a computer. You'll need an Android file manager that allows you access to the entire file system, not just the "sdcard" type area. I use SolidExplorer, but Root Explorer would work just as well. Your goal is to get the file /system/framework/framework-res.apk on your Android device onto your computer. There are probably a dozen ways to accomplish this. Super noob method: just copy this file from its original location to your "Downloads" folder, then plug your device into your computer via USB and copy the file out of the Downloads folder and onto your computer using MTP. Another method would be to send it to yourself as an attachment on an email. Hell, Solid Explorer has a SMB/SAMBA client built into it, so if you know how to use that you can just push the file directly from its original location to a shared folder on your computer. If you need a step-by-step on how to accomplish this particular step, IMO you're not tech savvy enough to be doing this stuff.
Anyways, so you should now have the framework-res.apk file from your current ROM on your computer.
Download and unzip my FrameworkFlasher-MOD file. Inside the folder, you'll see several folders and files. You need to put the original framework-res.apk file in the "place-framework-res-here" folder (how inscrutible!). Then you can run RunMe.bat.
You should get a pop-up window with a simple text-based menu. You'll want to run Option 1. The program will process for a while, and then should end up at a "The APK has been decompiled successfully" message. You can press any key to continue. At this point its not a bad idea to just leave FrameWork Flasher running.
FrameWork Flasher should have unpacked all the resources from the APK into the folder "files-to-edit". You'll need to go into files-to-edit\framework-res.apk\res\values. Inside of their, you'll find a bunch of XML files. You need to open bools.xml in the text editor of your choice. You're looking for the line that says
<bool name="config_voice_capable">false</bool>
All you need to do is change false to true, so you should end up with
<bool name="config_voice_capable">true</bool>
Then, save the file and close your text editor and go back to FrameWork Flasher.
You'll now want to run through options 2, 3 and 4. After doing this, you'll have a file called "update.zip" in the "final-zip-file" folder. You'll need to put this onto your device and flash it.
If you've flashed ROMs before, I'd hope you know how to do this. As with the "get your framework file" step, there are many different possible ways to get the update.zip file onto your device. You could transfer via USB, over the network, via email, whatever.
Once you've got the file on your device, you flash it like you do any other flashable ZIP using CWM or TWRP. This ZIP should work with either recovery, and you do NOT need to clear cache or anything like that. Simply flash and then reboot your device.
NOTE FOR T-MOBILE USERS: Some T-Mobile customers, including me, get a "New Voicemail" notification on their device(s) with voice capable turned on. This is specifically a problem with the way your T-Mobile account was initially set up and/or provisioned. The device is correctly reporting the voicemail status it gets from your account. The problem is that T-Mobile sometimes puts the "Welcome to your new voice mailbox!" message into your inbox even if your voicemail is not turned on. As far as I know there's no way to fix this issue short of working with a T-Mobile tech to get them to fix it, which I haven't bothered trying to do given the weird nature of what I'm doing. In CM10.2 you can just swipe this message away. It occurs once and only once each time the device is rebooted. On the current builds of CM11, the voicemail notfication cannot be swiped away. This is a known bug in AOSP and was fixed in 4.4.2, so the fix should come to CM11 soon enough.
Forgot to mention, since this makes your device think its a "phone", if you install Dialer.apk, you can have access to the normal "Phone" app in your Apps drawer, and mess with SIP goodness
Also, for CyanogenMod users, your ROM probably did not come with some APKs that will make this more useful.
You CAN just use Google Hangouts as your SMS/MMS app, but some people may prefer to use the native CM app instead (it has those nice pop-up messages!). For that you need MMS.apk.
If you want to mess with the "Phone" functionality, you'll need Dialer.apk.
And finally, if you want to receive emergency notifications from the government (for like natural disasters and Independence Day-style alien invasions and stuff ) you'll need CellBroadcastReceiver.apk. Please note that none of these are needed for SMS functionality and all these APKs are from CyanogenMod and will not work on stock or other ROMs.
For CM10 Stable, I grabbed these APKs out of the Nexus 4 (mako) ROM, stuck them in a zip and uploaded them here.
On CM11-M1. same deal but I used the Nexus 5 (hammerhead) ROM as my source. Those are here.
These files just need to be placed into the appropriate folder(s) on your device and then you'll need to set the file ownership & permissions the same as the rest of the the stuff in there (owned by root:root, -rw-r--r-).
They all go in /system/app, except for MMS and Dialer on CM11. On KitKat they have introduce the new /system/priv-app folder. My ZIPs contain those directories to remind you where to put the stuff.
I'm not a Windows user and I'd love to modify my own (stock) framework-res.apk to re-enable SMS support. Do you know what tools FrameWork Flasher uses "behind the scenes" to decompile and recompile the apk?
I don't like the idea of tampering with framework-res.apk using apktool unless somebody can confirm that this is the right direction.
sbiriguda said:
I'm not a Windows user and I'd love to modify my own (stock) framework-res.apk to re-enable SMS support. Do you know what tools FrameWork Flasher uses "behind the scenes" to decompile and recompile the apk?
I don't like the idea of tampering with framework-res.apk using apktool unless somebody can confirm that this is the right direction.
Click to expand...
Click to collapse
APK Tool is indeed the right direction to take.
I actually had to update the binary of APK tool that Framework Flasher uses, since the one included in the original isn't new enough to know what JellyBean and KitKat are Since FrameWork Flasher is a Windows Batch Script, I'm certain its just automatically doing stuff in the command line you could be doing by hand.
Looking at the source, I think the deompilation is done with this command:
java -Xmx%heapn%m -jar apktool.jar d "../place-framework-res-here/framework-res.apk" "../files-to-edit/framework-res.apk"
"%heapn%" is a variable, which appears to default to the value of 64.
So the command
"java -Xmx64m -jar apktool.jar d "/path/toframework-res.apk" "/path/to/extract/to"
should work on Linux or Mac, provided you've got Java installed and the jar in the current working directory. Obviously change the paths to match your local stuff. Post how it works if you'd like, I'love to update the guide to include Mac / Linux instructions, and Framework Flasher is the only "Windows" part about it.
DivinityCycle said:
Post how it works if you'd like, I'love to update the guide to include Mac / Linux instructions, and Framework Flasher is the only "Windows" part about it.
Click to expand...
Click to collapse
Obviously I messed up the resulting framework-res.apk because it got stuck in a Zygote startup loop. It's worth noting that I built apktool from the latest git sources, so there might be some bugs lurking in the shadows.
Oh well, I'll just wait for somebody else to do the dirty work
sbiriguda said:
Obviously I messed up the resulting framework-res.apk because it got stuck in a Zygote startup loop. It's worth noting that I built apktool from the latest git sources, so there might be some bugs lurking in the shadows.
Oh well, I'll just wait for somebody else to do the dirty work
Click to expand...
Click to collapse
Well, if you send me your framework-res.apk I can mod it for you. Takes like 2 seconds
The Framework Flasher source code shows the following for the actual "do the work" steps:
To decompile the original APK-
java -Xmx%heapn%m -jar apktool.jar d "../place-framework-res-here/framework-res.apk" "../files-to-edit/framework-res.apk"
To compile the new APK-
java -Xmx%heapn%m -jar apktool.jar b %~dp0files-to-edit\framework-res.apk %~dp0place-framework-res-here\unsignedframework-res.apk
To sign the APK-
java -Xmx%heapn%m -jar signapk.jar -w testkey.x509.pem testkey.pk8 ../place-framework-res-here/unsignedframework-res.apk ../place-framework-res-here/signedframework-res.apk
To build the unsigned ZIP-
7za a -tzip %~dp0place-framework-res-here\unsignedframework-res.apk %~dp0temp-files\* -mx%usrc% -r
And finally, to sign the ZIP-
java -Xmx%heapn%m -jar signapk.jar -w testkey.x509.pem testkey.pk8 ../final-zip-file/update_unsigned.zip ../final-zip-file/update.zip
note: you do not actually need to sign the ZIP. You CAN flash a zip without a signature on it, its just that with signature you get verification that the file is intact, which isn't a bad idea.
In Batch's screwy syntax, %heapn% is the variable that contains the heap size, and it looks like the default heap size the script uses is 64 unless otherwise specified by the end-user.
Also, %~dp0 is just a path expansion expression used to give the full path to the target files where its used.
I'm pretty sure you can make use of the jar and key files inside the FrameWork Flasher zip file I attached to this thread. You can find them in the resources folder. Both apktool.ar and signapk.jar are necessary, and I'm pretty sure the testkey files are needed to do the digital signatures and make this stuff work. Hope that stuff helps
Your mediafire link is just another link to download 7zip, could you update it. Thanks.
deyanimay said:
Your mediafire link is just another link to download 7zip, could you update it. Thanks.
Click to expand...
Click to collapse
Damn you multi-tasking!!! sorry about that. Fixing it nao.
The link should be http://www.mediafire.com/download/jozlg1xy4vxiegb/FrameworkFlasher-MOD.zip
when I tried to use framework flasher option 1 it said
Framework Flasher 1.1.4 - by Wes Foster (wesf90)
Please read the "Help" section before using this script
--------------------------------------------------------------------------------
----
Compression: 9 Heap Size: 64mb
````````````````````````````````````````````````````````````````````````````````
````
Main Options (in order)
-----------------------------------
(1) Decompile APK
(2) Compile APK
(3) Sign APK
(4) Create and Sign update.zip
(5) Great News! (when your finished creating the zip)
Other Options
-----------
(10) Set Compression Level for APK's
(11) Set Max Memory Size (if you get stuck when decompiling/compiling)
(12) Read Logs
(13) About / How-to / Help
(99) Exit
--------------------------------------------------------------------------------
Choose the number corresponding to the option:1
(removing old files...)
(removing old files-to-edit...)
===============++ Decompiling the APK. Please, please be patient ++==========
=====
ECHO is off.
An error has occurred. Check the log for more info.
ECHO is off.
Press any key to continue . . .
Click to expand...
Click to collapse
I attached the log. I'm trying to do this with CM 11 M1 on my deb, windows 8. Any ideas?
edit: framework-res.apk i'm trying to decompile: https://www.dropbox.com/s/iqc3eniv0u51ytg/framework-res.apk
seems like this is a common problem (googled it echo off) but I havent found a solution that works
edit 2: just tried it on my windows 7 laptop with the same result
edit 3: tried doing this with the cm 10.2 framework-res.apk with the same result.
About the voice mail message. Have you tried to install T-mobile Visual Voicemail to see if it could download then delete the message? I don't know how this app works, it's just the first thing I thought of when I read your post.
Thanks for creating this quide. I tried the single steps of the guide two weeks ago (I described it here: http://forum.xda-developers.com/showpost.php?p=47928887&postcount=167), but always got a bootloop. (De-)compiling the framework succeeded without errors and I tried it with and without changing the build.prop. By now I have no clue what went wrong. Mabye you need a special version of apktool fitting the rom you want to patch ?
Paten said:
About the voice mail message. Have you tried to install T-mobile Visual Voicemail to see if it could download then delete the message? I don't know how this app works, it's just the first thing I thought of when I read your post.
Click to expand...
Click to collapse
I've tried this and it doesn't work. I guess the app can't properly add the visual voicemail service to that line. I've also asked T-mobile about it and they said that I don't even have a voicemail box to store messages so there is nothing they can do about it.
nsmart said:
Thanks for creating this quide. I tried the single steps of the guide two weeks ago (I described it here: http://forum.xda-developers.com/showpost.php?p=47928887&postcount=167), but always got a bootloop. (De-)compiling the framework succeeded without errors and I tried it with and without changing the build.prop. By now I have no clue what went wrong. Mabye you need a special version of apktool fitting the rom you want to patch ?
Click to expand...
Click to collapse
Same here, it appears that setting config_voice_capable to true triggers an NPE inside the Keyguard class (i.e. the system PIN entry dialog) which then in turn causes SystemUI to restart over and over.
Perhaps the answer lies somewhere in the changes between 4.4 and 4.4.2 inside the AOSP device tree for deb, but I don't have the time to do an extensive diff of everything that has changed between those two releases.
Has anybody succeded in modding the stock KOT49H build without side effects?
---EDIT---
Apparently @GuyAdams managed to do it. Question is, how
cheers mate, nice post etc, been trying to get this going the last few days (and trying the other posts I've seen you talking on) but so far no luck. I'm getting the same log error as the previous poster too.
cheers
running nexus 7 with cm11 latest nightly.
burpitt said:
cheers mate, nice post etc, been trying to get this going the last few days (and trying the other posts I've seen you talking on) but so far no luck. I'm getting the same log error as the previous poster too.
cheers
running nexus 7 with cm11 latest nightly.
Click to expand...
Click to collapse
Well that sucks! It looks like APKtool doesn't work on anything newer than 4.4. I was able to reproduce the errors by trying to decompile / recompile the framework-res.apk from stock 4.4.2. The current release of APKtool from Slimbean I found here on XDA Devs appears to not be new enough. The main attraction of FrameWork Flasher over other solutions was the extremely easy & rapid download & use (as opposed to the end user having to like go download and install the entire Android dev kit), and Virtuous Ten Studio can definitely do this job, but again it looks to be an order of magnitude more complex for the average user to use. I'm going to be a little busy today doing actual work, but I should be able to find the time to work on this other stuff as well. Frustrating!
Is this working for the rom here: http://forum.xda-developers.com/showthread.php?t=2545628
And what about the carrier dont they see you now making calls and texts on a line that is set to be a tablet?
curtdragon said:
Is this working for the rom here: http://forum.xda-developers.com/showthread.php?t=2545628
And what about the carrier dont they see you now making calls and texts on a line that is set to be a tablet?
Click to expand...
Click to collapse
Did you even read my post? At no point did I say anything about "making calls", and as stated in the OP, this simply turns on the software on the tablet that allows you to send & receive SMS/MMS messages. You have to have to actually have SMS service to send / received SMS messages.
Also as carefully stated in OP, using CM10 or CM11 means you can use Voice+ to make Google Voice messages act like regular SMS.
Last but not least, the most recent builds of Bruce's CM11 ROM (the one you linked to) already have this modification applied (as he explained in the most recent few posts).
DivinityCycle said:
Did you even read my post? At no point did I say anything about "making calls", and as stated in the OP, this simply turns on the software on the tablet that allows you to send & receive SMS/MMS messages. You have to have to actually have SMS service to send / received SMS messages.
Also as carefully stated in OP, using CM10 or CM11 means you can use Voice+ to make Google Voice messages act like regular SMS.
Last but not least, the most recent builds of Bruce's CM11 ROM (the one you linked to) already have this modification applied (as he explained in the most recent few posts).
Click to expand...
Click to collapse
Hey thanks for coming off as a douchbag. Do I even read? No, perhaps you've edited your post several times since i did. Not to mention the fact that your title reads "Enable SMS on any ROM" then you go on to say that it will also enable the voice portion of the phone. Finally I asked a legitimate question it he texts why? because with ATT i have a share plan. While the plan says it's unlimited talk and text then the data is shared each device is different on the account and priced differently as well.
Also if I wanted to use Google Voice to send text messages i would just do that. Voice+ sends
But as you said this is enabled in the ROm i am using so I will exit this thread now.
You really need work on your people skills.
I do not run framework flasher is not possible to have a zip ready to be flash? I have a nexus 7 2013 LTE with cm 11 kot49h.... Thanks
Inviato dal mio Nexus 7 utilizzando Tapatalk