[ROM] ApeX 1.3.1 for Droid X - Running, running, as fast as it can (12/16/10)

[devortex]

Google Voice Search for bluetooth

I've got a question that's been making me crazy.

The voice command app from motorola is crazy slow, and when I tried some aosp style roms, they had it removed. With that app removed, I was able to use the google voice search app from the market with my bluetooth headset.

I've tried freezing the voice commands app, and completely uninstalling it via titanium backup(this made blur really mad with a billion fc warnings until I restarted). No matter what I do, I cannot get my bluetooth headset to work with google's voice search. If I long press the button on the headset, it'll open up the dialer and do a quick redial, but a short press just causes two quick beeps. My guess is that something in blur, or the bluetooth drivers are forced to use the voice commands app.

Is there any workaround for this? sux, because I cannot even restore voice commands for some reason. Titanium backup says its all good, but it's not there and still shows up in the list of missing apps. Maybe a restore is needed to recover it?

If anyone has any advice on how to safely and completely remove voice commands, it'd be greatly appreciated. :heart:

 

[hyperlite]

I've got a question that's been making me crazy.

The voice command app from motorola is crazy slow, and when I tried some aosp style roms, they had it removed. With that app removed, I was able to use the google voice search app from the market with my bluetooth headset.

I've tried freezing the voice commands app, and completely uninstalling it via titanium backup(this made blur really mad with a billion fc warnings until I restarted). No matter what I do, I cannot get my bluetooth headset to work with google's voice search. If I long press the button on the headset, it'll open up the dialer and do a quick redial, but a short press just causes two quick beeps. My guess is that something in blur, or the bluetooth drivers are forced to use the voice commands app.

Is there any workaround for this? sux, because I cannot even restore voice commands for some reason. Titanium backup says its all good, but it's not there and still shows up in the list of missing apps. Maybe a restore is needed to recover it?

If anyone has any advice on how to safely and completely remove voice commands, it'd be greatly appreciated. :heart:

Yeah, I suspect a data wipe would fix this. TiB can be very useful, but it can also cause a lot of issues. Have you tried uninstalling and reinstalling voice search from the market?

Sent from my DROIDX using Tapatalk

 

[devortex]

I've got a question that's been making me crazy.

The voice command app from motorola is crazy slow, and when I tried some aosp style roms, they had it removed. With that app removed, I was able to use the google voice search app from the market with my bluetooth headset.

I've tried freezing the voice commands app, and completely uninstalling it via titanium backup(this made blur really mad with a billion fc warnings until I restarted). No matter what I do, I cannot get my bluetooth headset to work with google's voice search. If I long press the button on the headset, it'll open up the dialer and do a quick redial, but a short press just causes two quick beeps. My guess is that something in blur, or the bluetooth drivers are forced to use the voice commands app.

Is there any workaround for this? sux, because I cannot even restore voice commands for some reason. Titanium backup says its all good, but it's not there and still shows up in the list of missing apps. Maybe a restore is needed to recover it?

If anyone has any advice on how to safely and completely remove voice commands, it'd be greatly appreciated. :heart:

Yeah, I suspect a data wipe would fix this. TiB can be very useful, but it can also cause a lot of issues. Have you tried uninstalling and reinstalling voice search from the market?

Sent from my DROIDX using Tapatalk

Yeah, I removed voice search and re-installed it a few times, threw in some reboots just for good measure. It works for everything except the bluetooth.

I just got voice commands working again by ripping the apk out of the apex1.3.zip file and using terminal to move it to system/app.

so far so good getting it back to where I was, but man, I wish I could use google voice search for bluetooth. The voice commands app takes ~20 seconds each time I try to use it via bluetooth.

 

[hyperlite]

I've got a question that's been making me crazy.

The voice command app from motorola is crazy slow, and when I tried some aosp style roms, they had it removed. With that app removed, I was able to use the google voice search app from the market with my bluetooth headset.

I've tried freezing the voice commands app, and completely uninstalling it via titanium backup(this made blur really mad with a billion fc warnings until I restarted). No matter what I do, I cannot get my bluetooth headset to work with google's voice search. If I long press the button on the headset, it'll open up the dialer and do a quick redial, but a short press just causes two quick beeps. My guess is that something in blur, or the bluetooth drivers are forced to use the voice commands app.

Is there any workaround for this? sux, because I cannot even restore voice commands for some reason. Titanium backup says its all good, but it's not there and still shows up in the list of missing apps. Maybe a restore is needed to recover it?

If anyone has any advice on how to safely and completely remove voice commands, it'd be greatly appreciated. :heart:

Yeah, I suspect a data wipe would fix this. TiB can be very useful, but it can also cause a lot of issues. Have you tried uninstalling and reinstalling voice search from the market?

Sent from my DROIDX using Tapatalk

Yeah, I removed voice search and re-installed it a few times, threw in some reboots just for good measure. It works for everything except the bluetooth.

I just got voice commands working again by ripping the apk out of the apex1.3.zip file and using terminal to move it to system/app.

so far so good getting it back to where I was, but man, I wish I could use google voice search for bluetooth. The voice commands app takes ~20 seconds each time I try to use it via bluetooth.

:/ I know. The stock voice commands app is really clunky.

Sent from my DROIDX using Tapatalk

 

[devortex]

Yeah, I suspect a data wipe would fix this. TiB can be very useful, but it can also cause a lot of issues. Have you tried uninstalling and reinstalling voice search from the market?

Sent from my DROIDX using Tapatalk

Yeah, I removed voice search and re-installed it a few times, threw in some reboots just for good measure. It works for everything except the bluetooth.

I just got voice commands working again by ripping the apk out of the apex1.3.zip file and using terminal to move it to system/app.

so far so good getting it back to where I was, but man, I wish I could use google voice search for bluetooth. The voice commands app takes ~20 seconds each time I try to use it via bluetooth.

:/ I know. The stock voice commands app is really clunky.

Sent from my DROIDX using Tapatalk

The good thing is that I only use my BT headset like once a week, so this is by no means a deal breaker for the Apex rom. I'm loving it too much to let this little stock nuisance distract me. dancedroid

 

[GameGrave]

great work with all this, Fab! I just got my droid X two weeks ago and I'm quickly learning all this rom and flashing gibberish! I have a question though - im running your 1.0.2.2 version of Apex on my 2.3.15 OTA. I'd like to update to your new version of Apex, so I'm going to have to get the new OTA which is available for me to update to, according to my phone. My question is, will my phone still work properly if i get the update for 2.3.340 right now with your 1.0.2.2 running, or do I need to go back to the stock droid x build before updating? thanks!

I just went through this today. Here is what I did:

1. Made a Nandroid backup of my current ROM.
2. Located my original stock Nandroid backup (Froyo 2.2) and restored it
3. Updated the .340 update and brought my phone to current state
4. Double checked Kernel, Baseband, Version, etc. with what is current to make sure I upgraded
5. Made a Nandroid backup of my stock .340 build
6. Loaded Apex 1.3.0 from the zip file
7. Wiped Cache / Data (I also did a format of the system and cache, and reinstalled Apex again... but I wanted to make sure I started from scratch, so I re-installed Apex once again after formating the system & cache)
8. Rebooted
9. Verified that the install took and double checked my version numbers on everything.
10. Made a Nandroid backup of my clean Apex 1.3.0 system

Worked great for me. I'm sure it is just a placebo effect, but the phone seems a lot faster and smoother than even when running 1.0.2.2. Not one reboot either!!!!

thanks nadious, everything went well, no problems yet. thank god for backup assistant! seems fast! im glad that the small gb keyboard issue was fixed with this version of the rom too... thanks again to fab! i'll be donating soon, when im not poor.

 

[droidxchat]

speaking of voice commands

I'm really surprised that in the .34 update moto didn't fix the security flaw. If you don't know what the flaw is... you can bypass any lockscreen (even with a lock on it) by simply holding down the search button for a moment (behind the scenes, this will bring up voice commands) and saying something like "call voicemail", after a moment the screen will switch to dialer where it will be calling voicemail and you can just end the call and be back at homescreen, successfully having bypassed the lockscreen. i guess moto just never got around to updating the voice command app.

an application called homesmack will allow you to fix this by installing a modified voice command app. haven't read through your problem completely plower.net but maybe homesmack could help you.

EDIT: I think I'm using the terms "voice search app" and "voice command app" interchangeably, even though they might be two different things, apologies.

 

[miller922]

Swype Beta

Has anyone had any issues with the Swype Beta? Swype has had some improvements since the version that was put on the Droid X, so I've been using that instead of the regular version. Well, with ApeX 1.3, I got it Swype Beta up and running, but if I restart the phone, Swype stops working properly. It will type with button presses, but it won't Swype. Clearing its data, uninstalling, clearing data on the installer, uninstalling that, rebooting, and then reinstalling it all gets it working again. Any ideas?

 

[Srt4tl]

First off Great job Fab! Best Rom ive used! Will be donating asap!

But my question is..
No matter what i try to switch the keyboard to the MT one in terminal it keeps telling me "Not Found"
Everything else on this ROM has been amazing just cant get the BMT or WMT keyboard back on my phone through terminal...
Thanks in advance!

 

[CD95YJ]

Dumb question but are you making sure the hyphen is there "keyboard -bmt"? Im using the black keyboard and had no problems switching, also are you granting su permission before trying to change? Try those and see if that works

Sent from my DROIDX using DroidForums App

 

[devortex]

speaking of voice commands

I'm really surprised that in the .34 update moto didn't fix the security flaw. If you don't know what the flaw is... you can bypass any lockscreen (even with a lock on it) by simply holding down the search button for a moment (behind the scenes, this will bring up voice commands) and saying something like "call voicemail", after a moment the screen will switch to dialer where it will be calling voicemail and you can just end the call and be back at homescreen, successfully having bypassed the lockscreen. i guess moto just never got around to updating the voice command app.

an application called homesmack will allow you to fix this by installing a modified voice command app. haven't read through your problem completely plower.net but maybe homesmack could help you.

EDIT: I think I'm using the terms "voice search app" and "voice command app" interchangeably, even though they might be two different things, apologies.

I thought the moto/vzw release notes mentioned fixing that problem. Maybe I read it wrong.

I've never actually tested it before, so maybe I'll try that later while I'm not in a cubical farm .

Voice Command is the motorola/verizon (not sure who to blame) app that does the exact same job as google's voice search. Only problem is that it does it poorly.

Google voice search, as previously mentioned, is google's android standard voice search application.

Both allow you to talk into your phone and say "call john", or "dial 1800...." or "email jimmy". Just the voice command app is in some way hard coded on the X to work with a headset even though the google voice search is installed and can be used for pretty much everything else like holding the search button.

Edit: Here's the release paper.
-second bullet from the bottom under the phone image says "Device lock remains, even after long, hard key press".... Sounds dirty lol.

 

[Tim-H]

Maybe this is a stupid question or concern but in the new gallery there's no option to resize pictures or do any editing other than crop or rotate. Does anyone know if there are plans to add these features to the gallery at a later time, or if I'm just missing something obvious. If no to both of those, is there a recommended application to download and pair up for editing? Thanks

ROM is perfect, this is the only issue I've had. It's not even that big of a deal.

 

[thepolishguy]

Maybe this is a stupid question or concern but in the new gallery there's no option to resize pictures or do any editing other than crop or rotate. Does anyone know if there are plans to add these features to the gallery at a later time, or if I'm just missing something obvious. If no to both of those, is there a recommended application to download and pair up for editing? Thanks

ROM is perfect, this is the only issue I've had. It's not even that big of a deal.

open the app Android Terminal and type in...

su

then type in

gallery

if you want your options back -switch back to the motorola gallery. type in...

gallery -mot

make sure to include the dash and put it in the right place. space after gallery, -mot, no space between the dash and the mot.

I was not a terminal user before this rom and it took me like 2 hours to figure out what I was supposed to type and where everything was supposed to go. I know -I am lame.

hope that helps. good luck.

 

[SCDroid]

how exactly do i need to word the scripts in emulator to remove madden and nfs shift?

 

[matalo]

Problem using Yahoo Mail with AOSP

I am fairly confident this is due to my not using the Blur email app.

I get yahoo notifications but cannot open the emails. When attempting, the screen blanks for a second and then returns to menu. I am using AOSP instead of Blur.