WebOS Internals - User contributions [en]

How To Remove VoiceDial

2011-09-13T02:22:37Z

Crimsonredmk:

= Summary =
For those plagued by the buggy and inaccurate VoiceDial that comes with webOS 2.1 (meta-doctor or otherwise), here's how to disable/remove it as cleanly as possible.

= Background =
All the VoiceDial packages in webOS 2.1:

<nowiki>#</nowiki> ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

= Disable System Service =
The simplest and easiest way to stop VoiceDial from getting in your way and crashing the MediaServer (kills system sounds) is to simply disable the service from starting at boot-time. This requires NO file / file system alterations:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Reboot. You'll be VoiceDial free. The codecs and such will still be loading and the actual app will still be there, but it won't work anymore so you won't have it randomly popping up and killing MediaServer.

= Complete Removal (No Way Back) =
If you have absolutly NO desire to EVER re-install it, then you can simply:

<nowiki>#</nowiki> mount -o remount,rw /
<nowiki>#</nowiki> for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
<nowiki>#</nowiki> mount -o remount,ro /
<nowiki>#</nowiki> ldconfig

Then:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time. There is no way to "re-install" VoiceDial with this method. The next method ''can'' make it possible to "re-install" VoiceDial.

= Complete Removal (Reversible) =
If you even ''THINK'' you ''may'' want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to a tarball in /media/internal/VoiceDialBackup, remove all the packages, and remove the service from boot-time:

<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvpf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

= Restoring =
You need to have the meta-doctor repo still available to pull out the .ipk's for VoiceDial. If you did a "make clobber", simply re-run the build script for your model phone.

<nowiki>#</nowiki> user@aragorn /srv/meta-doctor $ find -iname '*voice*ipk'
./build/preplus-p101ueu-wr-2.1.0/carrier/contacts.plugin.pmvoicecommand_1.0-2_all.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-dede_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-engb_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-enus_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-eses_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-esmx_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-frca_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-frfr_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-itit_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand_1.4-5.30_armv7.ipk

Install those .IPK's back onto your device:

1) Plug your device into a computer with a '''functioning''' novacomd.
2) cd /srv/meta-doctor/build/preplus-p101ueu-wr-2.1.0/carrier/ (or where ever you have your meta-doctor build directory).
3) for IPK in *voice* ; do palm-install -d usb $IPK ; done
4) novaterm -d usb
5) <nowiki>root@My Pre:/#</nowiki> mount -oremount,rw /
6) <nowiki>root@My Pre:/#</nowiki> tar -xvpf /media/internal/VoiceCommandBackup/VoiceCommandExtras.tar.gz -C /
7) <nowiki>root@My Pre:/#</nowiki> ldconfig
8) <nowiki>root@My Pre:/#</nowiki> mount -oremount,ro /
9) <nowiki>root@My Pre:/#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'
10) <nowiki>root@My Pre:/#</nowiki> reboot

Everything should be back to it's MediaServer killing norm!

Meta Doctor

2011-09-10T04:12:02Z

Crimsonredmk: Redirected page to Application:MetaDoctor

#REDIRECT [[Application:MetaDoctor]]

Meta-Doctor

2011-09-10T04:10:57Z

Crimsonredmk: Redirected page to Application:MetaDoctor

#REDIRECT [[Application:MetaDoctor]]

Bootie

2011-08-22T02:20:23Z

Crimsonredmk:

'''Current Version''': 191.4 for WebOS 1.4.1 <BR>
Old version : 145.2.6 for WebOS 1.0.3

stage3 bootloader of the device, unpacked from the end of boot.bin. loaded to **0x82000000** in memory and looks very similar to iBoot from the iPhoneOS devices.

Getting into bootie mode is as easy as holding the volume-up key while plugging the phone into USB while the phone is in the "off" state. The novaterm/novaproxy programs can then be used to talk to bootie.

The example help:

<pre><nowiki>
] help
command list:
nduid : get the device id
usb : usb transfer commands
lboot : boot linux image
klog : klog commands
printenv : print all of the environment variables
getenv : read an environment variable
setenv : set an environment variable
reset : reset the device
script : run a script at specified address
run : run a script at from an environment variable
return : return from current script
help : this list
version : get bootie version
battery : battery status (found in webOS 1.4.1 and not in 1.0.3)
charging : commands to set charging states
fsboot : boot current image based on environment
chainboot : boot another bootloader image based on environment
go : Jump to a given address with the given arguments
cpurev : read the cpu revision (found in webOS 1.0.3 but not in 1.4.1)
diag : perform diag operations: write, boot, verify
poweroff : power off completely
</nowiki></pre>

The default environment during boot:

<pre><nowiki>
] getenv
T ? = 0
T chargebypass = 0
T framebuffer = 0x8f600000
T boardtype = castle-dvt3
installer = trenchcoat
T klog_len = 0x100000
T klog_addr = 0x8ff00000
T logofile = boot/logo.tga
T bootaddress = 0x81000000
T bootfile = uImage
T bootfs = ext2
T bootdevice = mmc0p1
T bootargs-ramdisk = root=/dev/ram0 ramdisk=32768 ro
T bootargs = root=b302 rootdelay=2 ro
T bootconsole = tty1
autoboot = fsboot
</nowiki></pre>

Here is the boot environment on a TouchPad (3.0.2):
<pre><nowiki>
T ? = -1000
T framebuffer = 0x7f600000
installer = trenchcoat
checkbatt = 1
T chargebypass = 1
T klog_len = 0x100000
T klog_addr = 0x7ff00000
T tablet_wod_support = 0x0
T extended_timeout = 0x0
T chainbootdevice = mmc0
T bootaddress = 0x41000000
T bootdevice = mmc0p12
T bootfile = uImage
T bootfs = ext2
T bootargs-ramdisk = root=/dev/ram0 rw
T bootargs = root=/dev/mmcblk0p13 rootwait ro
T bootconsole = ttyS0,115200n8
T autoboot = fsboot
T boardtype = topaz-Wifi-pvt
</nowiki></pre>

Another trick while bootie is active:

novacom get file://klog