Been toying around with getting the genius button app working on the Nexus and I think I have it working. Got it to read and send text messages but am having issues doing web searches keep receiving "sorry no network connection" (although I believe that is because my network sucks in my computer room)
Here are the steps if anyone is interested.
Push both files in system.zip to your system folder, and both files in lib.zip to your lib folder. I used rootexplorer to just copy the files over.
I am on Modaco's Desire rom but I suspect the same thing may work on CM, not 100% sure.
Credit to Firerat i pulled the files from his Mytouch slide rom.
http://dl.dropbox.com/u/5070738/system.zip
http://dl.dropbox.com/u/5070738/Lib.zip
This apparently gives you another keyboard using dragon dictation but it fails at voice command due to network error. Any help or clues on how to fix this.
You think this would work on Froyo 2.2?
-------------------------------------
Sent via the XDA Tapatalk App
i think the vlingo app has similar function u guys should try it's good
Related
This issue has been resolved - Tutorial posted at the link below.
http://forum.xda-developers.com/showthread.php?t=736433
Not the answear you waiting but i have a hero that id like to flash to metro... any idea? Link? Thanks
Sent from my PC36100 using Tapatalk
well I can tell you it can be done with everything working but mms. my brother in law has the solution and his ego is working on cricket with everything but mms.
Sent from my PC36100 using Tapatalk
Same here. I have an Evo on Cricket including market and apps except for MMS. The autostart/u2nl method for the Eris works on the Evo using the same autostart.sh script (unmodified). However the 3G connection is flaky and times out frequently. Also I get random Data Call error 98 messages related to Sprint stuff still on the phone. (I'm running a rooted stock 2.1 ROM)
I also noticed that during the toast root process I was able to ##778# (quite to my surprise) then it went away when I flashed the whitslack update ROM (upgrades radio, wimax, etc).
The strange thing re: MMS is that I tried the APN backup/restore option which worked on the Eris and it "appears" to work. The configuration settings within the Message application "look" right for Production but alas I still cannot receive or send pic messages. No biggie (I ain't paying someone just to get MMS working) but would be nice to have it working. Seems like overkill to have to create an entire ROM just to get MMS working.
Anyway...it's quite frustrating since the Eris works perfectly on Cricket with the autostart/u2nl solution.
##778# and any other ## command doesnt work for me anymore. any ideas to fix?
davebu said:
##778# and any other ## command doesnt work for me anymore. any ideas to fix?
Click to expand...
Click to collapse
don't use dialer one.
using the stock dialer, running fresh 0.5.3. whats a market alternative? btw it worked before it just doesnt work anymore.
kthejoker20 said:
don't use dialer one.
Click to expand...
Click to collapse
What alternative is there to access ##778 options other than the dialer?
fritzel67 said:
What alternative is there to access ##778 options other than the dialer?
Click to expand...
Click to collapse
Anycut can link to EPST settings.
Chances are the reason it works in one rom and not another is due to the apk's installed. look for differences in the framework folder - the lib folder - and the /system/app folder from your rom that is working the rom that is not.
I belive the EPST settings are native to stock HTC roms and thus not included in a cyanogen based rom (thats how it is on the eris at least). Most people on the phone's true network will never need EPST so it may be getting removed by the rom developer to cut down on space and increase speed etc.
just my thoughts.
Are we not even allowed to say the S word anymore around here?
rayden25 said:
Are we not even allowed to say the S word anymore around here?
Click to expand...
Click to collapse
Actually you are I deleted it because after I deleted the app, it turned into a PM me *wink wink* deal. Discussion is fine, just no posting the actual app or a link to get the app
i wasn't invited, i was curious about how i could get swype on my phone too.
Crimton said:
i wasn't invited, i was curious about how i could get swype on my phone too.
Click to expand...
Click to collapse
I know, but per a letter from the developers to us, unless swype is native on a device, it should not be posted
i have the swype apk, i was just hoping there was a mod for the g-tablet that would allow swype to install. that wouldn't involve posting a link.
theimpaler747 said:
I deleted it because after I deleted the app, it turned into a PM me *wink wink* deal.
Click to expand...
Click to collapse
I wouldn't do that *wink wink*
rayden25 said:
I wouldn't do that *wink wink*
Click to expand...
Click to collapse
I'd hope not
I tried the official beta, as I'm a member, and a SGS version both on my G-Tablet and they install but wont open as the resolution is not supported. If there's a apk that does actually work. I'd love to just KNOW that. and I'll find it myself.
Thanks!
I tried using the swype from my epic but when I installed it and enable it it just FCs. I did use slideit but the keyboard took up most of the screen. Anybody else have any luck?
This is also something I am very interested in and have yet to get it to work.
I made the changes that rothnic suggested in the build.prop, loaded the lib, and dropped the ap in system/app and my tab doesn't see it at all. I've loaded a ' few' different versions on it that install but just fc. I've spent hours on it with no luck yet.
I'm not giving up hope for someone to release and update.zip but I'm not going to bother rothnic about it (anymore) as I'm sure he's working on roms and such. Even if he weren't, he's done more than his share here and I'm sure one of us will get it.
I'm still working it myself and if I make any progress I will surely let everyone know.
Just a reminder we can't post the .apk for swype here, as we don't want the thread pulled, again.
Sent from my GT-I9000 using XDA App
it2steve said:
This is also something I am very interested in and have yet to get it to work.
I made the changes that rothnic suggested in the build.prop, loaded the lib, and dropped the ap in system/app and my tab doesn't see it at all. I've loaded a ' few' different versions on it that install but just fc. I've spent hours on it with no luck yet.
I'm not giving up hope for someone to release and update.zip but I'm not going to bother rothnic about it (anymore) as I'm sure he's working on roms and such. Even if he weren't, he's done more than his share here and I'm sure one of us will get it.
I'm still working it myself and if I make any progress I will surely let everyone know.
Just a reminder we can't post the .apk for swype here, as we don't want the thread pulled, again.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
It sounds like you are doing something wrong when copying it over. It should come up under keyboards in settings. You would enable it there, then long press on an input box to switch to it.
I just did this a second time today and can confirm that it works.
rothnic said:
It sounds like you are doing something wrong when copying it over. It should come up under keyboards in settings. You would enable it there, then long press on an input box to switch to it.
I just did this a second time today and can confirm that it works.
Click to expand...
Click to collapse
yea, I was hoping that was the case but there can't be much that can go wrong. Download it or copy over via usb... then use root explorer to put it under system/app
For some reason I cant get ADB to work anymore? It had at one time. Do we know of any known issues with flashing that we loose the ability to ADB?
Oh well... I am a patient person and it's not like its a deal breaker for me. All is working pretty smoothly 3 weeks into the game.
Swype / ADB ... Progress / NO Progress
Ok, this is VERY interesting...
I still cant get swype to work. I FINALLY got to ADB push the .apk and the Lib and triple checked the build.prop (even used a couple different ones).
All I get is an FC over and over and when I got to settings-applications-manage, to clear cache, it's grayed out. I booted into recovery and cleared dalvik cache, wipe cache, and data. I have even gone as far as to re-flash the ZPAD 1.1, load gApps, Market Hack, Open GL Hack, and restart the whole swype process again with the same result.
HERE IS THE INTERESTING PART and we may want it posted elsewhere: I couldn't get my win7 to load the proper ADB driver (even though it had worked before). I found an app call ADBWireless (widget). It allows me to hit the widget and connect through ADB wirelessly (local wifi) and push/pull ect.
This was amazing and easy to use. Of course you have to have the Tab up so it wouldn't help for anyone who's in a loop.
When you hit the widget it shows the local ip address to connect to:
-I go to the command prompt \androidsdk\tools and type:
adb connect 192.xxx.xxx.xxx:5555
-it connects, and I am able to see the device
I have to use adb remount and then I'm good to go.
Hope this helps someone down the road. I'll keep checking back here but feel free to PM me if you have any questions (or find an update.zip for swype to work).
I made a little progress last night, got rid of the FCs but I can't get the keyboard enabled in the Settings. I managed to track down a Swype version from a Samsung Gaxlaxy Tab, at least that is what I think it is from, and then I had to find the necessary Lib file from somewhere else but when I push the .so to the Lib through ADB and install the Apk it seems like I'm closer, I can open the Swype settings screen and change things but I just can't get the keyboard enabled in the settings and then of course I can't pick the Swype keyboard when configuring the input method.
What changes were you making to the build.prop?
bmasephol said:
I made a little progress last night, got rid of the FCs but I can't get the keyboard enabled in the Settings. I managed to track down a Swype version from a Samsung Gaxlaxy Tab, at least that is what I think it is from, and then I had to find the necessary Lib file from somewhere else but when I push the .so to the Lib through ADB and install the Apk it seems like I'm closer, I can open the Swype settings screen and change things but I just can't get the keyboard enabled in the settings and then of course I can't pick the Swype keyboard when configuring the input method.
What changes were you making to the build.prop?
Click to expand...
Click to collapse
there was a 'header' so to speak that Rothnic posted that mad a few changes to the build.prop to make it look like portions of the Galaxy. He has it at the 'other' fourm.
Checked the permissions on the build.prop and they looked different. I couldn't just 'change' them in root explorer so I re-inserted the lines on the original build.prop, also did a fix permissions in CM (not that it helped).
Permissions in the lib file are hard to tell what they are supposed to be because several of the lib files there have different ones set. Swype.apk permissions look the same as the others. Still getting same FC's over and over. I was able to get into manage apps and hit force stop and clear (quickly tho) but goes back to the same after reboot.
Thanks for trying, as I said before, it's not a biggie. I just enjoy swype as being from palm and blackberry phone's if it weren't for swype I dunno that I would have kept an Android phone.
I can wait, I've spent too many hours jackin with it (although I did learn about the adb wireless and I am comfortable in pushing file that way now)
I managed to get it working although it is a little laggy. I followed rothnic's info in the other thread and after playing around with the build.prop file it is now working. Hopefully as the roms get faster this will get faster. Thanks for the help.
bmasephol said:
I managed to get it working although it is a little laggy. I followed rothnic's info in the other thread and after playing around with the build.prop file it is now working. Hopefully as the roms get faster this will get faster. Thanks for the help.
Click to expand...
Click to collapse
How did you do it? Can you be specific? Which version of Swype are you using? Where did you find it? What other thread?
Working on latest zpad rom. Had to set permissions - I think the important ones were r-x for User on both the lib and apk. And of course the build.prop edits.
-=Sent from my ViewSonic G Tablet using Tapatalk=-
I'm pretty sure the swype word is naughty here so I suggest you google for 'rothnic swype' and check the post on the other forum that comes up.
I used adb to push the modified build.prop to the sd card, along with the .so and .apk files. Then I used adb shell to copy the files to the locations rothnic specifies.
I just switched to the htc inspire 4g from the samsung captivate. i loved to memo app on the captivate but cant seemed to get it on my inspire. ive found the apk. but still havnt been able to get it to run. any suggestions?
I would like to do the same???
I think it needs deoxed but I do not know How.
View attachment Memo.apk
Place that app in your sdk tools folder press shift and left click on the folder open command prompt
Adb remount
Adb push ./ apps name (space)/system/app
Or put on your SD card and installfrom there.
edit: nvm I miss read hold on Ill find out.
Sent from skynet using XDA Premium Resistance App
Has any1 gotten it to work? And what rom?
I wouldn't mind trying it... just cautious incase it soft bricks
Maedhros said:
Has any1 gotten it to work? And what rom?
I wouldn't mind trying it... just cautious incase it soft bricks
Click to expand...
Click to collapse
won't soft brick, probably just has something to do with the framework would be my guess. It wont install though.
Evernote
I also have the Samsung Captivate and also switched tot the HTC Inspire. I downloaded the app Evernote. I like it more than the Memo app and your notes (which you can add pictures to) is all uploaded to your Evernote account. So if you switch devices all your information switches over much like Contacts with your Google account.
Day after day I sit around and search for a solution to the receiving a small mms problem. I post on every thread I find about it and even pm but I get no response or just condescending responses. Has anyone found a solution to this? I have T-Mobile and I'm running revolution hd 6.1.1. With the stock radio (or so I think). Please someone help this is becoming unbearable
Sent from my HTC Inspire 4G using XDA App
Does you're internet work in 2G?
Sent from my HTC Desire HD using xda premium
::Slowly turns head in anticipation of bad news:: yyyyeeeaa why?
Sent from my HTC Inspire 4G using XDA App
Maybe being a little more descriptive would help. What is "a small mms problem?" Are the messages truncated, the type too small, are messages not being sent or received, are the messages unreadable, is the text in the wrong language, is the icon lost?
Maybe a little more information about your problem would help someone here recollect a solution they applied to a similar problem.
1. I do not have T-Mobile
2. That being said, I was experiencing issues with small MMS pictures in the first few weeks of xda development for the Inspire
3. Searching, I came across something suggesting you change device information in build.prop to mask it as another device and it worked for me
4. I can't find that information anywhere - but this will do the same thing, masking your device as a device tmous will recognize
5. build.prop will automatically be backed up doing it this way, so if you want to go back after you're done you can - but it may be worth a shot
Don't know if this would work or not - I had a similar problem with a ROM in the first few weeks of flashing (note: I am NOT on TMobile, but was having the tiny mms problem), and I found a guide suggesting to edit build.prop to disguise it as a nexus. It worked for some reason...but I can't for the life of me find this walkthrough. The following steps will accomplish the same thing, disguising it as a phone tmous knows. It's worth a shot (backup first)..
1.) Download “Root Explorer” or a simpler application
2.) Open Root Explorer and go into the System folder
3.) One in the System folder, hit the Mount R/W at the top right
4.) Hold down on Build.prop file and then open it in the text editor
5.) Change the following lines
Here are the changes you need to make:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys
6.) Hit menu and Save & Exit. You’ll get a message explaining that the original build.prop file was saved as build.prop.bak
7.) Reboot and try MMS again
This issue has been around for a long time, dating back to windows mobile, there have been fixes found and they work till the next update and then it's broke again. I would try the above. Then if that doesn't work if you really want to fix it. I would find one of the fixes for the WM version and see what was done and see how it can be moved to android. I have also heard that a 3rd party SMS app fixes it as well, nit sure about that though.
It is an issue with t-mobile and you will be hard pressed to find a solution in the inspire forum. I don't know what the fix is but I can assure you if you go to the sensation forum, or others where the roms are not t-mobile specific but the phone is widely used on that network, you will see what is changed by looking into the fix zips provided.
thanks for the responses everyone i will give the theories a try when i have the chance tomorrow hopefully something will work.
Hey yall I am trying to restore my Sprint VVM and I have downloaded a few random APKs from xda and pushed them to system and they are fizzling out in the long run. Glitchy and not working properly.
If anyone has some files they know will work on JB, CM10 or CM10.1 please post up or point me in the right direction. I think others will find this info useful as well as most people prefer VVM to google voice and the loss of VM in CM builds is unbearable.
Can someone pull the file from the soak test? Is there a link to the soak test file still where I can try and pull it?
TIA
Did you check this thread? OP says it works on CM10.
I've tried both of these, one comes from the post linked above, and neither of them work. The 3mb file at least stays open without crashing but it never retreives any voicemails.
Anyone, be sure and let me know if/how you get these to work.
I just copied the one that was on my stock ics seems to work fine for me.... i remember it upgraded once cant remember if i was onn the jb soak or not
Sent from my XT897C using xda app-developers app on CM-10.1
Matt2k12 i got an apk off of google in pushed to system/app. Its works but a work around persay. If you receive a voicemail. Your notified through the text message. It says call 605******* but doesnt work. What does work is hold down 1 in the dial pad. It calls your voicemail and you enter yur password and then you get your voicemail. I also got the 9016 message with it as well. But regardless you have the ability to listen to your voicemail. I have the apk that im using for this to work but dont now how to upload it to xda. If you know how to please tell me.my vvm is version 5.3.0.30
Sent from my XT897C using xda app-developers app
arbosus said:
I just copied the one that was on my stock ics seems to work fine for me.... i remember it upgraded once cant remember if i was onn the jb soak or not
Sent from my XT897C using xda app-developers app on CM-10.1
Click to expand...
Click to collapse
I went into my stock asanti C zip using Solid Explorer and moved over 2 apk files that were both in the system/app folder. First was SprintVoiceMail.apk @ 64.78kb. Second was VVM.apk which was 3.58mb. I thought I needed them both since they were both in that zip file. But when I rebooted I had 2 voicemail apps. The 64kb one direct dials VM and the 3.5mb one obviously is the VVM app. I successfully sent the activation text ([email protected]) and got some sort of confirmation message on screen (forget now) and then I even sent a VM to myself to test it. It took a few minutes to come in but it did. But then I got a call a little bit later and the guy left me a message cuz I got the 9016 but I never got the VVM notification. Indeed, its not in my VVM inbox either. Can you please confirm which of these files you have in your system/app folder? Did you install or extract to those files or simply move/copy to from the zip as I did?
TIA
I just copied the vvm apk to system/app and rebooted. When i get a voicemail i dont get a notification in the app either. But i get a text thst says the phone number that left the voicemail. Then i hold 1 in the phone dialer and it calls voicemail and i listen to the voicemail. I know its eritating not being able to use the app itself but at least you have the ability to listen to voicemail
Sent from my XT897C using xda app-developers app