Database Users

VoiceDialer on stock ADP1

So I wanted VoiceDialer on my stock ADP1. I grabbed VoiceDialer.apk from JFv1.31_ADP1.zip and installed it using adb (sdcard mounted on computer, so it wasn't mounted on the phone). It runs, and I was quite satisfied with its recognition abilities, but when it comes to clicking "OK" to dial, it always crashes with a "force close" dialogue. Holding the "send" button does bring up the VoiceDialer program. My guess is I'm missing some sort of configuration somewhere. Does anyone know?

Make sure you grabbed the VoiceDialer.odex too, if there is one.

Koush said:
Make sure you grabbed the VoiceDialer.odex too, if there is one.
Click to expand...
Click to collapse
I didn't find any odex files (unless they would be in recovery.img, which I haven't yet learned how to open). These files are not created automatically?

Unzip a RC30 update.zip and look in \system\app\
On ADP1, the dex is created at runtime by the dalvikvm from the classes file inside the zip. On RC30, the dex files for the builtin apps are created ahead of time and stored alongside the apk. This prevents the system from using up \data partition space with dex files (As the ADP1 build does).

jashsu said:
Unzip a RC30 update.zip and look in \system\app\
On ADP1, the dex is created at runtime by the dalvikvm from the classes file inside the zip. On RC30, the dex files for the builtin apps are created ahead of time and stored alongside the apk. This prevents the system from using up \data partition space with dex files (As the ADP1 build does).
Click to expand...
Click to collapse
I was able to find a copy of VoiceDialer.odex as per your description, but if I understand you correctly, that will not solve my problem.
If the dev phone uses dex files instead, and these are created at runtime, then I would expect to find a dex file for VoiceDialer if everything is working properly. Indeed, the file "[email protected]@[email protected]" exists.
Any other hints as to why the application might crash after clicking "OK" to dial a number?

Yeah just grab the VoiceDialer.apk from JF's modified ADP1 build. It contains the classes.dex file required to run on ADP1 build.

jashsu said:
Yeah just grab the VoiceDialer.apk from JF's modified ADP1 build. It contains the classes.dex file required to run on ADP1 build.
Click to expand...
Click to collapse
That's what I did initially. That part all seems to work.

Doh, went around in a circle ;-) I thought we were talking about the RC30 version.
Yeah you'll have to ask JF about this since I think he compiled VoiceDialer from source for his ADP mod build. There is no odex file to look for.

jashsu said:
Yeah you'll have to ask JF about this since I think he compiled VoiceDialer from source for his ADP mod build.
Click to expand...
Click to collapse
Yeah, I'm sure JF could see the problem real quick. I'm real timid about bothering people, though - I was hoping he might swing by this thread by chance. What's considered appropriate on this forum: PM? E-mail? IM? Visitor Message?

IMSargon said:
Yeah, I'm sure JF could see the problem real quick. I'm real timid about bothering people, though - I was hoping he might swing by this thread by chance. What's considered appropriate on this forum: PM? E-mail? IM? Visitor Message?
Click to expand...
Click to collapse
Your best bet is IRC. A lot of us hang out in #android on Freenode.

IMSargon said:
So I wanted VoiceDialer on my stock ADP1. I grabbed VoiceDialer.apk from JFv1.31_ADP1.zip and installed it using adb (sdcard mounted on computer, so it wasn't mounted on the phone). It runs, and I was quite satisfied with its recognition abilities, but when it comes to clicking "OK" to dial, it always crashes with a "force close" dialogue. Holding the "send" button does bring up the VoiceDialer program. My guess is I'm missing some sort of configuration somewhere. Does anyone know?
Click to expand...
Click to collapse
Your best bet is to remount /system and push the .apk directly into /system/app. I haven't tried installing it with adb install, so I'm not sure if that's what is causing your problems or what.

JesusFreke said:
Your best bet is to remount /system and push the .apk directly into /system/app. I haven't tried installing it with adb install, so I'm not sure if that's what is causing your problems or what.
Click to expand...
Click to collapse
Yeah, I had the same problem (I've installed voice dialer using adb install)
Uninstalled in application manager, rebooted, remounted, pushed voicedialer.apk to /systemp/app, rebooted again, and it worked )

JesusFreke said:
Your best bet is to remount /system and push the .apk directly into /system/app. I haven't tried installing it with adb install, so I'm not sure if that's what is causing your problems or what.
Click to expand...
Click to collapse
It worked! Great! Thanks a ton!
------------------------------
Steps taken:
1. copy VoiceDialer.apk to phone
# adb push VoiceDialer.apk /sdcard/VoiceDialer.apk
763 KB/s (51125 bytes in 0.065s)
#
2. enter shell on phone, and gain root
# adb shell
$ su
#
3. mount the system partition as rewritable
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#
4. copy VoiceDialer.apk to the proper system directory
# cat /sdcard/VoiceDialer.apk > /system/app/VoiceDialer.apk
#
5. make permissions match the other files
# chmod 644 /system/app/VoiceDialer.apk
#
6. reboot the phone
# reboot
------------------------------
For extra credit, does anyone understand why this happens? What does it tell us about how apps work and install?

adb pushing the apk directly bypasses the PackageManager. By using adb install, the package manager will run (as if the package was installed from the Market or Browser). There are various reasons the PackageManager might reject a package, including inability to run dexopt, incompatibility with existing data registered to an older version of an app, etc. A list of errors that would block an apk installation is here. Look at the constants starting with INSTALL_FAILED and INSTALL_PARSE_FAILED.

jashsu said:
adb pushing the apk directly bypasses the PackageManager. By using adb install, the package manager will run (as if the package was installed from the Market or Browser). There are various reasons the PackageManager might reject a package, including inability to run dexopt, incompatibility with existing data registered to an older version of an app, etc. A list of errors that would block an apk installation is here. Look at the constants starting with INSTALL_FAILED and INSTALL_PARSE_FAILED.
Click to expand...
Click to collapse
Interesting, but in this case the application did not fail to install. The installation went normally, and the application functioned normally up to the point where it attempted to interface with another application/subsystem (whatever dials the phone).

IMSargon said:
Interesting, but in this case the application did not fail to install. The installation went normally, and the application functioned normally up to the point where it attempted to interface with another application/subsystem (whatever dials the phone).
Click to expand...
Click to collapse
When you install it with adb install, it gets installed as a normal (non-system) application. This can be verified by checking /data/system/packages.xml:
Code:
<package name="com.android.voicedialer" codePath="/data/app/VoiceDialer.apk" [B]system="false"[/B] ts="1232083952000" userId="10029">
<sigs count="1">
<cert index="0" />
</sigs>
</package>
One of the permissions it requires is "android.permission.CALL_PRIVILEGED". Based on the info in frameworks/base/core/res/AndroidManifest.xml (in the git source):
Code:
<permission android:name="android.permission.CALL_PRIVILEGED"
android:label="@string/permlab_callPrivileged"
android:description="@string/permdesc_callPrivileged"
[B]android:protectionLevel="signatureOrSystem"[/B] />
You can see the protectionLevel is "signatureOrSystem", meaning that the application has to be a system application in order to use that permission. Since the voice dialer was not installed as a system application, it can't be assigned that permission.
To confirm this, I tried installing the voice dialer with adb install, and then took a look at the logcat output, which contains the following line:
Code:
01-15 23:32:32.903: WARN/PackageManager(56): Not granting permission android.permission.CALL_PRIVILEGED to package com.android.voicedialer (protectionLevel=3 flags=0x44)
However, when you copy the apk to /system/app, it gets installed as a system application, which can be verified again by looking at /data/system/packages.xml:
Code:
<package name="com.android.voicedialer" codePath="/system/app/VoiceDialer.apk" [B]system="true"[/B] ts="1232084484000" userId="10035">
<sigs count="1">
<cert index="0" />
</sigs>
</package>
So it is able to use the "android.permission.CALL_PRIVILEGED" permission. After coping the apk to /system/app, I checked the logcat output and there was no mention of not being able to grant the android.permission.CALL_PRIVILEGED permission, as expected.
Interestingly enough, copying the file to /system/app doesn't bypass the package manager. The package manager is watching both /data/app and /system/app for new files, and it automatically installs anything you copy into either location. It also does an uninstall when you delete an apk from either location.

JesusFreke said:
Interestingly enough, copying the file to /system/app doesn't bypass the package manager. The package manager is watching both /data/app and /system/app for new files, and it automatically installs anything you copy into either location. It also does an uninstalls when you delete an apk from either location.
Click to expand...
Click to collapse
I didn't know that. In that context it does make sense why it would disallow call permission if put into /data/app
Offtopic, but are you planning on creating a modified version of the newly released ADP1 "1.1" build?

Thanks, JF, your explanation makes the problem quite clear!

[Q] (q)What system apps can i remove

I am wondering if someone would make a list of system apps that would be safe to remove.I know I can remove pulse because ive done it before.

http://forum.xda-developers.com/showthread.php?t=1411953

Thanks for the link

Rooted and with superuser.apk.
All I have removed.(Just necessary apps left, in basis of stock 6.2.2)
amazonmp3-unsigned.apk -- Music player
AmazonVenezia.apk -- Amazon app store
ATVAndroidClient.apk -- Video player
AudibleAndroidApplication-venezia.apk -- Audible book
CalendarProvider.apk -- Calendar
Cloud9-release-unsigned.apk -- Amazon browser
Cloud9SystemBrowserProvider-unsigned.apk-- Amazon browser
com.amazon.dcp.apk -- About Amazon registration
Contacts.apk -- Contact
ContactsProvider.apk -- Contact
CSApp-unsigned.apk -- Amazon app
DownloadProvider.apk --
DownloadProviderUi.apk --
Email.apk -- email
Facebook.apk
IMDb-2.3.apk -- Movies
KindleForOtter.apk -- kindle book read app
LatinIME.apk XXX Only after you install another input app, this is the original input app
Launcher.apk XXX Only after you install another launcher app
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
oem_install_flash_player_signed.apk -- Don't remove it if you want to see adobe flash in browser
OOBE-unsigned.apk -- Kindle reader component
OtterTutorial.apk -- Kindle manual
OTASilentInstall.apk -- Kindle On The Air update app
PicoTts.apk -- Text To Speech
Pulse-amazon.apk -- News reader app
Quickoffice_AMAZON_4.1.467_VC.apk -- Office component
QuickSearchBox.apk
TtsService.apk -- Text To Speech
VisualizationWallpapers.apk
Windowshop.apk
My suggestion is :
create a folder named "app_backup" under /system, then move the above into it.
While your KF cannot startup, you can use following adb commands to restore apps.
Win7 32bit code:
c:\adb\adb shell
>su
>mv /system/app_backup/*.* /system/app
My apps installed.
Opera browser
Root Explorer
ES explorer
Good luck!

Removing system applications (Needs root)

reading this thread http://forum.xda-developers.com/showthread.php?t=1217134
I removed some apps from /system/app
AdService.apk and AdService.odex is needed for Android Market / Google Play
blur_yahoo.apk and blur_yahoo.odex should not be deleted or contacts app crash (force close)
Update:
BlurEmailEngine.apk && BlurEmailEngine.odex needed by SMS/MMS app
The included swype (dated version)can be removed, but you also have to remove a library so file.
To remove swype keyboard
Delete:
/system/app/Swype.apk
/system/lib/libSwypecore.so
Click to expand...
Click to collapse
<< link >>
Backup of /system/app folder and libSwypecore.so (Source Stock Atrix 4G 4.5.141.MB860.AtT.en.US; Android 2.3.6; N_01.77.37P)
https://docs.google.com/folder/d/0B6vGhPKpea7pQ0czZENVVWR2Q0U/edit
List of files in /system/app
Anyone with experience about deleting apps from /system/app ?

[Q] Which system APK files are required for the ROM to run?

SOLVED
I wanted a completely clean ROM to start developing on. I have looked at CleanROM, but it has too many system apps.
These are the system APKs the ROM is currently running with.
Code:
ApexLauncher.apk
Bluetooth.apk
CertInstaller.apk
ConfigUpdater.apk
DefaultContainerService.apk
DownloadProvider.apk
DownloadProviderUi.apk
FusedLocation.apk
HTMLViewer.apk
InputDevices.apk
KeyChain.apk
LatinImeDictionaryPack.apk
LatinImeGoogle.apk
MediaProvider.apk
MediaUploader.apk
Nfc.apk
PackageInstaller.apk
Settings.apk
SettingsProvider.apk
Superuser.apk
SystemUI.apk
UserDictionaryProvider.apk
XT9IME.apk

Honestly the stock Nexus 7 build is pretty damn clean.
If you want to experiment with disabling APKs, try the built-in disable functionality in Settings / Applications / All. Any system app that can be safely disabled (and some that can't) will have a Disable button. This is safer to try out than zapping apk files yourself. If something goes wrong after disabling an app, you'll know you need it back.

I have narrowed down the APKs and it is working fine, but now the middle home navigation button doesn't do anything. I suspect it is one of the google search apps that I deleted, but which one? I always assumed the navigation bar was handled by systemUI. :/

Forty.Two said:
I have narrowed down the APKs and it is working fine, but now the middle home navigation button doesn't do anything. I suspect it is one of the google search apps that I deleted, but which one? I always assumed the navigation bar was handled by systemUI. :/
Click to expand...
Click to collapse
Did you disable the launcher by accident?
Also I have heard that the OS immobilizes the home button until initial device setup is complete and then lets it work. Maybe it has something to do with that.

Thanks!
cmstlist said:
Did you disable the launcher by accident?
Also I have heard that the OS immobilizes the home button until initial device setup is complete and then lets it work. Maybe it has something to do with that.
Click to expand...
Click to collapse
It was the setupwizard.apk! I deleted it to make changes too the ROM faster.
It makes perfect sense too. The power menu had limited options, the battery drop down bar was gone, and the home button wasn't working. Just like during the setup!
This is what I did to bypass the setupwizard.apk when it start up:
1. Launch adb shell
2. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
3. Exit shell and issue an adb reboot.
4. Delete setupwizard.apk if you want
Now the ROM works fine with only 23 APK files in the /system/apps folder! That is a great improvement compared to the original 85.

Blaupunkt Cape Town 945 firmware and apps?

I quite like the UI design of the Blaupunkt 945. It has good looking (IMO) radio and dab apps as well. I tried to google the apps in case someone had extracted them from their player but couldn't find anything.
What I did find, however, is the official download page for the unit, which includes rom updates. Upon unzipping the downloaded update file, there are several big img.lzo archives. While I managed to decompress the lzo-archives, I have no idea how to get a look inside the .img files. Does anyone have any ideas? The files can be downloaded here:
http://www.blaupunkt.com/en/nc/serv.../?uid=6609&tx_ddfservicedoku_pi1[view]=single
Latest firmware appears to be from 20th Feb 2017.
Hopefully it's possible to extract apps from these image-files.

nyogtha said:
Hopefully it's possible to extract apps from these image-files.
Click to expand...
Click to collapse
Most probably those img files are disk images. Are they named something like kernel.img, boot.img, misc.img, system.img, recovery.img?
Edit: The SD.zip is password protected. I assume that what you are trying to do is not entirely legal.

I agree, they are probably disk images, but I'm not sure which type. As for the password, it's in the readme that comes with the download, with a typo though

nyogtha said:
I agree, they are probably disk images, but I'm not sure which type. As for the password, it's in the readme that comes with the download, with a typo though
Click to expand...
Click to collapse
It is an ext4 disk image
This is the content of /system/app
Code:
AndroidPlayer.apk
ApplicationsProvider.apk
app.lnk
AuxIn.apk
AVoff.apk
BackCamera.apk
BackupRestoreConfirmation.apk
Bluetooth.apk
Browser.apk
Calculator.apk
Calendar.apk
CalendarProvider.apk
CarLink.apk
CertInstaller.apk
Contacts.apk
ContactsProvider.apk
DefaultContainerService.apk
DeskClock.apk
Disc.apk
DownloadProvider.apk
DownloadProviderUi.apk
DrmProvider.apk
Email.apk
Exchange2.apk
FileExplorer.apk
ForyouBlueTooth.apk
ForyouDAB.apk
ForyouDTV.apk
foryouMediaScanner.apk
ForyouUpdate.apk
Galaxy4.apk
Gallery2.apk
HoloSpiralWallpaper.apk
HTMLViewer.apk
InputDevices.apk
iPod.apk
KeyChain.apk
LatinIME.apk
Launcher2.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
logFile.apk
MagicSmokeWallpapers.apk
MediaProvider.apk
midwareDaemon.apk
midwareService.apk
Misc.apk
MusicFX.apk
MusicPlayer.apk
NightDisplay.apk
NoiseField.apk
PackageInstaller.apk
PhaseBeam.apk
Phone.apk
PicoTts.apk
Provision.apk
QuickSearchBox.apk
Radio.apk
Rear.apk
RtkDaemon.apk
Settings.apk
SettingsProvider.apk
SharedStorageBackup.apk
SoundRecorder.apk
SystemUI.apk
TelephonyProvider.apk
UserDictionaryProvider.apk
VarioColour.apk
VisualizationWallpapers.apk
VpnDialogs.apk
WAPPushManager.apk
So yes: it is fairly easy to extract apks from this img file. That is: if you are on linux. For windows see here.

Sweet! I did try to mount it quickly in Linux earlier but didn't have time when it didn't want to mount with auto fs type. Did you just use mount with type set to ext4?

nyogtha said:
Sweet! I did try to mount it quickly in Linux earlier but didn't have time when it didn't want to mount with auto fs type. Did you just use mount with type set to ext4?
Click to expand...
Click to collapse
make some folder like "system" inside the folder where you "lzop"-ed the system.img.lzo and mount a loop device on it.
Code:
mkdir system
sudo mount -o loop system.img ./system
Then you can access it as a "read-only" folder.

Thanks Managed to mount it and copied the apks out. Wonder if they will run on anything else. I'll have a go tomorrow.

I think we need someone with an mtcb unit to try these. Or if possible recompile for sofia.

nyogtha said:
I think we need someone with an mtcb unit to try these. Or if possible recompile for sofia.
Click to expand...
Click to collapse
I don't give you a high chance of success. To recompile you really need the source code, not something "decompiled" like done with apktool, jd-gui, dex2jar or the likes.
And just as important: As long as you don't know which radio chip and other hardware is used, you might be able to recompile but you will never be able to make it run on your hardware.
What you could try is to modify the look and feel (and RDS part) of the current Sofia radio app like Malaysk has done for the MTCB/MTCD units.

You're right. Sounds too complicated. If only the Klyde/Joying dab app was made by someone actually using dab... It works but it's VERY basic. No presets etc.

nyogtha said:
You're right. Sounds too complicated. If only the Klyde/Joying dab app was made by someone actually using dab... It works but it's VERY basic. No presets etc.
Click to expand...
Click to collapse
And the DAB is different. The DAB apk is used in conjunction with a USB DAB-stick. There is no DAB hardware in the head-unit. It is more likely to get that one to work than the normal builtin radio. As long as the DAB apk can find its own USB stick it is OK (and it USB not Universal Serial Bus? )
Having said (typed) that: I would not try that road either.