Develop Bugs

Which comands to use to replace stoch maps with maps(brut)

Hi everyone,
i', new here in the forum so i tried to find some answers to my question but so far no luck.
I'm using modaco r3 with ASD+ and i'd like to replace the stock maps.apk withe the maps(brut) with navigation.
Which comands do i have to use in recovery to remove the original maps.apk and install the maps(brut).apk to system/app??
Many thanks

settings > applications > MANAGE APPLICATIONS > uninstall google maps, install maps brut with some sort of filemanager.. estrong, astro, linda file manager or whatever..

I thoud this was unpossible wo system/apps acces.

well i want to push the maps(brut) into system/app... (first delete original maps)
isn't that possible on the desire?

Brut doesn't have to go in /system/app, as I recall. I believe I installed it and the navigation option before I ever had root, so there was never any chance of getting into /system.
If you really do want it to go in /system/app, then you need to:
Boot to recovery (get the green menu screen)
Get into an adb shell
Inside the shell, run "mount /system"
cd /system/app
ls (to find what the relevant apk is)
rm <packagename>.apk
exit
adb push <location of brut.apk> /system/app
Reboot
That should be it. I take no responsibility, have a full nandroid backup, etc etc etc, but that's all you have to do.

thanks
i don't have to unmount system?

thanks
i don't have to unmount system?
Click to expand...
Click to collapse
I don't think anything else is running that would even require the /system partition, as otherwise it would have mounted it itself, so don't worry about it.

do you really need the [brut] map now that the stock map has navigation?

fowler002 said:
do you really need the [brut] map now that the stock map has navigation?
Click to expand...
Click to collapse
Its only available in the UK and US afaik
Theres more to earth than just the two of you ;D

[GUIDE] 11/22/2010 - Restore Swype after upgrading to CyanogenMod

If you were like me, you rushed right into installing CyanogenMod. Whoops, found out there is no swype installed. What to do?
Hopefully you made a nandroid backup like me. I didn't want to do a full nandroid restore just to extract the files. So I did this...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
UPDATED 11/22/2010 - Okay, some people have requested a "newbie friendly" solution. I have created an APK which will help automate this procedure, without the need for ADB. If you have already applied CyanogenMod, then use this APK to select an older Clockwork Backup that has your licensed Swype. It will then extract and install the files for you. I have only tested on the G2.
http://www.mediafire.com/?j7dnv321ej0mrch
I'll possibly do some updates to:
a) cache swype for future installs (to make restores super quick)
b) add other extractions of 'your' saved files (i.e. google apps)
c) add more options for handling cache/files/etc.
I hope this helps. Enjoy!
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
# --------------------------------------------------------------------------------------------
# How to recover your swype files from your nandroid backup
# Quick and dirty extract
# Prepare a staging area on your computer
mkdir nandtmp
cd nandtmp
# Copy your old nandroid (pre CM) backup to your staging area..........
# i.e. /androidbackups/clockworkmod/backup/2010-11-01.02.02.02
cp $WHEREVER_OLD_IMAGE_IS/system.img .
# extract files...
unyaffs system.img
adb remount
# Push the swype files back to your Android device
adb push ./system/lib/libSwypeCore.so /system/lib/
adb push ./system/app/Swype.apk /system/app/
# Some users have had issues with not seeing Swype in the options (possibly non read/write system?), so they just installed the APK. If you install it, make sure the lib file has been pushed first.
# i.e. adb install /sdcard/Swype.apk
# Update permissions for good measure (may not be needed)
chmod 644 /system/app/Swype.apk
chmod 644 /system/lib/libSwypeCore.so
# I rebooted, but have heard reports that it is not necessary
adb reboot
# Now in Menu>Settings:Language & keyboard unselect the Android keyboard and make sure Swype keyboard is checked.
A similar process can be done directly on your phone.
# --------------------------------------------------------------------------------------------
Hope that helps others restore Swype (or other files they desire) without having to do a full Nand restore.
-oldsk00lz

getting force close on swype as soon as I uncheck the android keyboard, not a huge deal but I do kinda miss swype

ranyvern said:
getting force close on swype as soon as I uncheck the android keyboard, not a huge deal but I do kinda miss swype
Click to expand...
Click to collapse
Did you push libSwypeCore.so to /system/lib yet?

For some reason it still doesn't show up in the keyboard list, any idea why?
Sent from my T-Mobile G2 using XDA App

Ok, what you're supposed to do is, you actually have to install the swype.apk. its not enough to copy it to the /system/app directory adb install Swype.apk or use root file explorer click on the apk file and choose install.
Sent from my T-Mobile G2 using XDA App

or you can open up cyanogenmod(unzip) and download a stock g2 rom and then just put the files in the proper places, then zip cm again and flash(i did this all from my phone ast night because i was too lazy to go to the computer)

have you tried to go to swype.com and signing up for there beta testing. Not sure if still open but does not hurt to try. I reinstall from the beta testing website and is working great on CM6.1 on my G2

k50aker said:
For some reason it still doesn't show up in the keyboard list, any idea why?
Click to expand...
Click to collapse
Be more specific. What have you done so far? Did you go into Settings > Keyboard and enable Swype yet?

I tried a few times before but could never get this dumb unyaffs to work for me.
i get
Microsoft Windows XP [Version 5.1.2600]
C:\g2orgsys>unyaffs systemg2.img
28852 [main] unyaffs 3212 _cygtls::handle_exceptions: Exception: STATUS_ACCESS
_VIOLATION
30677 [main] unyaffs 3212 open_stackdumpfile: Dumping stack trace to unyaffs.e
xe.stackdump
348883 [main] unyaffs 3212 _cygtls::handle_exceptions: Exception: STATUS_ACCESS
_VIOLATION
375003 [main] unyaffs 3212 _cygtls::handle_exceptions: Error while dumping stat
e (probably corrupted stack)
Idk im pretty lazy sometimes, if you can provide some help on this, i would GREATLY appreciate it.
oh and I tried, quickly, to get the emulator working but failed! Im sure its probably something ez I missed. :/

Stryder5 said:
Be more specific. What have you done so far? Did you go into Settings > Keyboard and enable Swype yet?
Click to expand...
Click to collapse
Yea, it wasn't there, again, in my case pushing it in to the /app folder did NOT work, I had to intall the apk maually like any other app. Of course only after pushing the lib file.
adb push libSwypeCore.so /system/lib
adb install Swype.apk
Unyaffs is supposed to work on windows? I didn't know that. I use linux, you sould try it and get used to it, it would save you a lot of trouble.
Sent from my T-Mobile G2 using XDA App

k50aker said:
Yea, it wasn't there, again, in my case pushing it in to the /app folder did NOT work, I had to intall the apk maually like any other app. Of course only after pushing the lib file.
adb push libSwypeCore.so /system/lib
adb install Swype.apk
Unyaffs is supposed to work on windows? I didn't know that. I use linux, you sould try it and get used to it, it would save you a lot of trouble.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Hmmm... I saw the swype in the settings after doing adb pushes and a reboot.
In reality, I had unchecked both Android keyboard, and Swype keyboard. Then went to a text field, and got a request for Android input. I then went back into settings and checked Swype, and then it just worked. I didn't need to install the APK. For those not seeing swype as an option, did you confirm that system was remounted and that files were copied? Did you reboot?
As for unyaffs, I was lazy. I just downloaded a binary for OSX from here: http://forum.xda-developers.com/showthread.php?p=7931772 . I haven't tried a Windows version of unyaffs.
-oldsk00lz

k50aker said:
Unyaffs is supposed to work on windows? I didn't know that. I use linux, you sould try it and get used to it, it would save you a lot of trouble.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
thats kinda sucks. lil more trouble then I was hoping for but I got a few LiveCDs somewhere.
How hard would it be to get this running through adb shell, on the phone? lol

wilnotdie said:
thats kinda sucks. lil more trouble then I was hoping for but I got a few LiveCDs somewhere.
How hard would it be to get this running through adb shell, on the phone? lol
Click to expand...
Click to collapse
wilnotdie - You should be able to do this directly on your phone, as well. Of course, you would need to mount your system read/write and cp files versus adb push.
i.e.
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp /sdcard/nandtmp/system/lib/libSwypeCore.so /system/lib/libSwypeCore.so
cp /sdcard/nandtmp/system/app/Swype.apk /system/app/Swype.apk
Hope that helps.
-oldsk00lz

oldsk00lz said:
wilnotdie - You should be able to do this directly on your phone, as well. Of course, you would need to mount your system read/write and cp files versus adb push.
i.e.
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp /sdcard/nandtmp/system/lib/libSwypeCore.so /system/lib/libSwypeCore.so
cp /sdcard/nandtmp/system/app/Swype.apk /system/app/Swype.apk
Hope that helps.
-oldsk00lz
Click to expand...
Click to collapse
Oh mybad, not that way. Was thinking of using the phone as my linux box instead of a pc. In theory it should work, just need to compile for use on the phone?
But Im guessing its not gonna be this ez lol

I didn't do any ADB pushes I just used root explorer to move the libswype file to lib directory then used the installer on the root explorer to install and it loaded right up for me. Only problem I'm getting is the double tap to edit isn't working now for some reason.
I pulled the files from the ota_root_noboot.zip from
http://forum.xda-developers.com/showthread.php?t=836042

Okay here is what I did and it worked. Using SU File manager (found in the market if you search "root explorer") and on the stock ROM, copy the lib and apk files from /system/app and /system/lib. I copied them to the root of my sd card. Wipe everything and install CM and the addon. Grab SU File manager again and find the lib file on your SD card. copy it. There are two little buttons on the top of SU File manager with an S and a D. I pressed both of them to mount system and data as read/write. Go to system/lib and paste the lib file. Verify that it is there and since there are so many files sort by size its like 998kb. Then just use SU File Manager or astro or whatever to find Swype.apk on your sd card. Install it from there. With Astro click it and "open app manger." Then go to keyboard settings and enable it as an input method. Go to swype settings and it should not FC if you did this stuff correctly. Set your settings and enjoy! Oh yea dont forget to uninstall and refund SU File manager

Hey Jkoenig00 did you have any issues with the double tap to edit?

Worked flawlessly and now I have swype running on CM. This should be stickied or something!

So for those of us who don't know what ADB is or how to use it...
are we screwed?
Is there a noob friendly method?

convolution said:
So for those of us who don't know what ADB is or how to use it...
are we screwed?
Is there a noob friendly method?
Click to expand...
Click to collapse
You can use root explorer. Download one of the stock roms. Access it through root explorer and copy the 2 files from the stock rom folders to its respective folder on your device. Then install the apk from within root explorer. Set everything up in your keyboard settings and your golden. Can be done in minutes.
Sent from my T-Mobile G2 using XDA App

[Q] Pays room task.sh edit

Edit this tash.sh to remove or keep applications under system/app, I am not sure whether my edit as below is ok, as I edit data/app and system/lib too
http://forum.xda-developers.com/showthread.php?t=943258
rm /system/app/Swype.apk (I can't find libSwype.so under lib, I remove this to install Swype with a new language later)
rm /system/app/AdobeReader.apk (I'd like to install a newer version)
rm /system/lib/libAdobeReader.so (is it ok to remove? I can't update to newer version if I didn't delete it)
rm /data/app/FancyWidget_1.3.0.apk (not sure whether ok to remove data/app which Pays added , I have to use another app)
rm /data/app/Flashlight.apk

ink222 said:
Edit this tash.sh to remove or keep applications under system/app, I am not sure whether my edit as below is ok, as I edit data/app and system/lib too
http://forum.xda-developers.com/showthread.php?t=943258
rm /system/app/Swype.apk (I can't find libSwype.so under lib, I remove this to install Swype with a new language later)
rm /system/app/AdobeReader.apk (I'd like to install a newer version)
rm /system/lib/libAdobeReader.so (is it ok to remove? I can't update to newer version if I didn't delete it)
rm /data/app/FancyWidget_1.3.0.apk (not sure whether ok to remove data/app which Pays added , I have to use another app)
rm /data/app/Flashlight.apk
Click to expand...
Click to collapse
Should be ok.

Thanks, I will have a try

Apps That Are Safe to Remove/Rename/Freeze in CM7 [Updated 2/16/12]

I haven't seen anything posted about this so I figured I'd post the list of apps that I have renamed or removed in CM7. Some are apps that the tablet won't ever use and some are apps that I personally won't be using. I'm sure there are more but these are the ones I've done so far. Please note: When you rename phone.apk you will get a message saying that phone has stopped working and it will not stop popping up, just hold down your power button to reboot and it won't come up again.
ADW Launcher.apk (if you're using a different launcher)
Androidian.apk
AdroidTerm.apk
Bluetooth.apk
Browser.apk (if you're using a different browser)
Camera.apk
CarHomeGoogle.apk
Cyanbread.apk
CMStats.apk
CMUpdate.apk
CMWallpapers.apk ((if you're using a different wallpaper)
Contacts.apk
DeskClock.apk
Development.apk
DownloadPrividerUi.apk
DSPManager.apk
Email.apk
FileManager.apk
FOTAKill.apk
GenieWidget.apk (news and weather widget)
GoogleQuickSearchBox.apk
HTMLViewer.apk
LatinIME.apk (if you're using a different keyboard)
LiveWallpapers.apk (if you're using a different live wallpaper)
MagicSmoke.apk
Mms.apk
Music.apk (if you're using a different music app)
OneTimeInitializer.apk
Pacman.apk
Phone.apk (RENAME THIS LAST)
Protips.apk
RomManager.apk
SetupWizard.apk
SoundRecorder.apk
SpareParts.apk
Talk.apk
TelephonyProvider.apk
Visualization.apk
VoiceDialer.apk
DO NOT RENAME: ContactsProvider, GoogleCalendarSyncAdapter or GoogleContactsSyncAdapter you will end up with framework and/or GApps errors.

I have often wondered why alot of these were left in the ROM.

I always delete lots of those apk even before I flash the update.zip
you can add:
Protips.apk
packman.apk (maybe)
RomManager.apk

I've been wondering about this as well and have been both mucking around with the ROM zips as well as simply deleting things with Root Explorer as it's just plain silly for Phone to exist on the Kindle Fire.
jwilliamf said:
I always delete lots of those apk even before I flash the update.zip
you can add:
Protips.apk
packman.apk (maybe)
RomManager.apk
Click to expand...
Click to collapse
Just to pick your brain a bit: Are you simply editing the zip contents (seems safest) or are you actually extracting everything and then re-compressing it once you've removed the fluff?

You *can* keep SoundRecorder if you want to - and it makes sense ot include it in the ROM. True, the Kindle Fire doesn't have a built-in mic, but I have one of these mics and it works great. It just doesn't use the speakers if this mic is plugged in, since it's detected as a headset + mic.
http://www.amazon.com/Switcheasy-ThumbTacks-Microphone-touch-Black/dp/B0021IAJEG

Just curious, regarding Contacts.apk and Phone.apk...are the two interdependant or will Contacts work without Phone.
Seems to me that using Contacts synced to your G-Mail account would provide the e-mail addresses of your contacts (just ignore the phone numbers) for any e-mailing you might want to do from your Fire...

Aahz Pervect said:
Just to pick your brain a bit: Are you simply editing the zip contents (seems safest) or are you actually extracting everything and then re-compressing it once you've removed the fluff?
Click to expand...
Click to collapse
I just delete or rename them in the system/app folder using root explorer.
hdmunger said:
Just curious, regarding Contacts.apk and Phone.apk...are the two interdependant or will Contacts work without Phone.
Seems to me that using Contacts synced to your G-Mail account would provide the e-mail addresses of your contacts (just ignore the phone numbers) for any e-mailing you might want to do from your Fire...
Click to expand...
Click to collapse
Your contacts should show up in your gmail automatically, at least they do for me.

As I recall from previous posts, renaming such apks like phone and telephony will cause FC's in the settings menu and possibly other areas.
Sent from my Kindle Fire using Tapatalk

DesDr0id said:
As I recall from previous posts, renaming such apks like phone and telephony will cause FC's in the settings menu and possibly other areas.
Click to expand...
Click to collapse
This was addressed already:
airmaxx23 said:
Please note: When you rename phone.apk you will get a message saying that phone has stopped working and it will not stop popping up, just hold down your power button to reboot and it won't come up again.]
Click to expand...
Click to collapse
Edit: Just reread your post and realized my response isn't addressing the issue... I would erase this post if I could.

DesDr0id said:
As I recall from previous posts, renaming such apks like phone and telephony will cause FC's in the settings menu and possibly other areas.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
The only temporary issue is when renaming phone it, causes it to force close, once you reboot it doesn't happen again. I've had them all renamed for a day or so and I've been through a lot of the settings and have not had an issue.

Why rename when you simply evict? make up some extra space for yourself...
do it with adb... root explorer titanium, your fingers, out of /system/app/* and then their corpse cousins over in /data/data/* This is where I learned... http://wiki.cyanogenmod.com/wiki/Barebones.
Telephony, bluetooth, latinime, latinimetutorial mms phone street torch music dsp sound recorder talkback. com.amazon.mp3 was a hated app of mine since time immemmorial!
My routine when flashing CM nightlys on other phones is rather than take the time to clean up the rom for myself, i would just flash the full rom along with the gapps and then the titanium zip as a system file so its there when I get into android... then use the titty with a pre-determined list and just rip a lot of stuff almost 30-80MB and that gave me a LOT of breathing room on the G1/Dream.
When Titanium got down to the last app =Wifi Calling App the phone would go nuts.. and I always had to hit the reboot at the specific time to get it to reboot (if I missed that time, then I had to do batt-pull) get into recovery do wipe cache and dalvik, then reboot recovery then fix permissions and boot back.. and all was well.
the point is when you take out the music and telephony, especially DSP Manager, anything that uses audio is tied to other parts of the framework -- but its always fixable with a reboot and fix permissions.

androidcues said:
Why rename when you simply evict? make up some extra space for yourself...
do it with adb... root explorer titanium, your fingers, out of /system/app/* and then their corpse cousins over in /data/data/* This is where I learned... http://wiki.cyanogenmod.com/wiki/Barebones.
Telephony, bluetooth, latinime, latinimetutorial mms phone street torch music dsp sound recorder talkback. com.amazon.mp3 was a hated app of mine since time immemmorial!
My routine when flashing CM nightlys on other phones is rather than take the time to clean up the rom for myself, i would just flash the full rom along with the gapps and then the titanium zip as a system file so its there when I get into android... then use the titty with a pre-determined list and just rip a lot of stuff almost 30-80MB and that gave me a LOT of breathing room on the G1/Dream.
When Titanium got down to the last app =Wifi Calling App the phone would go nuts.. and I always had to hit the reboot at the specific time to get it to reboot (if I missed that time, then I had to do batt-pull) get into recovery do wipe cache and dalvik, then reboot recovery then fix permissions and boot back.. and all was well.
the point is when you take out the music and telephony, especially DSP Manager, anything that uses audio is tied to other parts of the framework -- but its always fixable with a reboot and fix permissions.
Click to expand...
Click to collapse
I always rename them and leave them for a few days before deleting them just to be sure things still play nicely.

Browser (I use silk)
Gallery (I use QuickPic)
ADW (I use go Launcher)

Aahz Pervect said:
I've been wondering about this as well and have been both mucking around with the ROM zips as well as simply deleting things with Root Explorer as it's just plain silly for Phone to exist on the Kindle Fire.
Just to pick your brain a bit: Are you simply editing the zip contents (seems safest) or are you actually extracting everything and then re-compressing it once you've removed the fluff?
Click to expand...
Click to collapse
Yes! Before flashing, open zip file and delete any apks that you don't need. Easiest way in my opinion.

Some more stuff you can safely remove (few already mentioned)
ADWLauncher.apk
Androidian.apk
AndroidTerm.apk
CMStats.apk
CMUpdateNotify.apk
CMWallpapers.apk
Development.apk
FileManager.apk
Livewallpapers.apk (Live wallpapers still work, just none are included)
MagicSmokewallpapers.apk
Protips.apk
SpareParts.apk
VisualizationWallpapers.apk

I created this little list of commands every time I install a new build of Cm7. Feel free to use it. ~30 apk's or so removed. Some stuff you might want to keep if you use it, be sure to remove from the command below, such as browser or gallery. I use other applications so I remove them
Code:
adb remount
adb shell
cd /system/app/
rm VoiceDialer.apk Androidian.apk AndroidTerm.apk Bluetooth.apk Browser.apk Camera.apk CarHomeGoogle.apk CMStats.apk CMUpdateNotify.apk CMWallpapers.apk Contacts.apk DeskClock.apk Development.apk DSPManager.apk Email.apk FileManager.apk Gallery3D.apk GenieWidget.apk LiveWallpapers.apk MagicSmokeWallpapers.apk Mms.apk Music.apk Pacman.apk Phone.apk Protips.apk RomManager.apk SoundRecorder.apk Talk.apk TelephonyProvider.apk VisualizationWallpapers.apk

Not trying to be an ass or anything but just removing the apk does not uninstall the app. The data will still be there and the device will sill think its installed (even tho you won't see the app in the app drawer) it shouldn't cause any issues but if your removing a bunch of stuff, might as well uninstall them correctly and reclaim the space they take up.
Titanium backup would probably be the easiest way to do it but what I prefer to do is put it all into a script. That way I can run it on whatever rom I install.
An example of how to uninstall the browser via command line...
rm/system/app/Browser.apk
pm uninstall com.android.browser
It should then say "seccess"
With system apps you need to remove the apk first then run the pm uninstall name.of.package command. Hope someone found this helpful
Edit: also, I wouldn't remove, uninstall or rename talk.apk because the market uses it in some way (can't remember for what exactly but it needs it)

foxdog66 said:
Not trying to be an ass or anything but just removing the apk does not uninstall the app. The data will still be there and the device will sill think its installed (even tho you won't see the app in the app drawer) it shouldn't cause any issues but if your removing a bunch of stuff, might as well uninstall them correctly and reclaim the space they take up.
Titanium backup would probably be the easiest way to do it but what I prefer to do is put it all into a script. That way I can run it on whatever rom I install.
An example of how to uninstall the browser via command line...
rm/system/app/Browser.apk
pm uninstall com.android.browser
It should then say "seccess"
With system apps you need to remove the apk first then run the pm uninstall name.of.package command. Hope someone found this helpful
Click to expand...
Click to collapse
Are you sure ;p
None of the apk's I removed show up in "/data/app" or "/system/app". So IMO, they are gone. Even checking the "/cache/" and it's contents. No trace of them there either. (I do wipe "cache/dalvik-cache" after deleting apk's).

foxdog66 said:
Not trying to be an ass or anything but just removing the apk does not uninstall the app. The data will still be there and the device will sill think its installed (even tho you won't see the app in the app drawer) it shouldn't cause any issues but if your removing a bunch of stuff, might as well uninstall them correctly and reclaim the space they take up.
Titanium backup would probably be the easiest way to do it but what I prefer to do is put it all into a script. That way I can run it on whatever rom I install.
An example of how to uninstall the browser via command line...
rm/system/app/Browser.apk
pm uninstall com.android.browser
It should then say "seccess"
With system apps you need to remove the apk first then run the pm uninstall name.of.package command. Hope someone found this helpful
Edit: also, I wouldn't remove, uninstall or rename talk.apk because the market uses it in some way (can't remember for what exactly but it needs it)
Click to expand...
Click to collapse
How do you find out what the name of each apk's matching package?

Takenover83 said:
Are you sure ;p
None of the apk's I removed show up in "/data/app" or "/system/app". So IMO, they are gone. Even checking the "/cache/" and it's contents. No trace of them there either. (I do wipe "cache/dalvik-cache" after deleting apk's).
Click to expand...
Click to collapse
Well the apk is gone but the /data/data/package data is still there. Try "adb shell pm list packages" and see if any of your removed apk's package names are listed.

Uninstall native APKs is so suicidal ?

Hello there
Is it really safe to uninstall native APKs on a CyanogenMod ROM ? I dislike to have several applications for the same job, we have a lot of storage problems with our old HTC Desire so a good cleaning is very important !
And if a remove some APKs in the ROM installation and repack ZIP is suicidal due to config installation ?
Do you have some tutorials and/or URLs to share ?
Thanks a lot in advance for your answers

Depends on the apk's you remove. I've been removing stuff on CM7 rom always.
This can get you started on what you should and should not remove.
http://wiki.cyanogenmod.com/wiki/Barebones

You can remove the following and still have "full" functionality:
Code:
Androidian.apk (theme)
Browser.apk (if you don't use the stock one)
Calculator.apk
Cyanbread.apk
CMWallpapers.apk
DSP Manager.apk
Email.apk
Filemanager.apk
FM.apk
Gallery3D.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
Music.apk
Pacman.apk
ProTips.apk
RomManager,apk
SpareParts.apk
SoundRecorder.apk
Stk.apk
Torch.apk
ThemeChooser.apk (No themes support)
ThemeManager.apk (No themes support)
VisualizationWallpaper.apk
VoiceDialer.apk

And remove these APKs directly on the ZIP installation file, then repacking the ZIP file and launch a complete flash on it... Safe or suicidal ? (yeah I like this word )

stankyou said:
Depends on the apk's you remove. I've been removing stuff on CM7 rom always.
This can get you started on what you should and should not remove.
http://wiki.cyanogenmod.com/wiki/Barebones
Click to expand...
Click to collapse
That's the source of goodness. Good job.

djdamage said:
And remove these APKs directly on the ZIP installation file, then repacking the ZIP file and launch a complete flash on it... Safe or suicidal ? (yeah I like this word )
Click to expand...
Click to collapse
There's nothing suicidal about accidentally removing critical apks on a rom and flashing it. I believe the worst you can get is a non-booting phone probably a usb brick maybe.. things that can still be fixed.
Flashing a corrupted hboot, now that's suicidal for your phone at least.

stankyou said:
Depends on the apk's you remove. I've been removing stuff on CM7 rom always.
This can get you started on what you should and should not remove.
Click to expand...
Click to collapse
I knew this source, however it's out-to-date now, most APKs are missing

It basically lists everything. What "most apk's" are you talking about that are not on the list?

djdamage said:
And remove these APKs directly on the ZIP installation file, then repacking the ZIP file and launch a complete flash on it... Safe or suicidal ? (yeah I like this word )
Click to expand...
Click to collapse
Do not repack the zip or you might be not able to flash it.
Just remove the files directly from zip archive.
I'm usually unpacking it just to see how big is the system to make smaller /system partition for few extra MB's internal memory. (custom hboot)
Sent from my HTC Desire using xda premium

It's easy and fairly safe to remove and/or add apks and/or configs to a zip ROM installation, even in /system, if you know for sure they aren't used by other apks.
I've done it many times.
But sometimes they might get somewhat corrupted and the recovery won't install them. If that happens try to make small changes each time and try them out.

I always remove unwanted .apks from the downloaded .zip file / custom rom prior to install.
You should use 7zip (Freeware - Google it) to open and browse the files in the .zip and delete the unwanted .apks. Everytime I have tried with WinRar it messes up the .zip file (wont install!), only works for me with 7zip (may work with Winzip too but untested by me).
The .apks can usually be found in sd-ext\app_s\ - depending on the rom you are installing.
N.b if your rom has the directories customize\app\ - don't delete the .apks in there as they are for the setup at rom install, are are selectable via the setup/install menu, deleting them may break the setup from completing.
Many .apks are deletable for example - I delete most widgets as I use a different launcher after install so they are useless to me.
e.g
com.htc.htcmsgwidgets3d.apk
com.htc.Sync3DWidget.apk
HtcAutoRotateWidget.apk
HtcDataRoamingWidget.apk
MMS.apk is the text message app and is deletable if your going to install something in its place after install. An example would be GO SMS.
Same with browser.apk - its the browser app. I delete it then after rom install I install something like Opera, Firefox or Dolphin etc.
DockMode.apk is for if you use a dock to connect your phone to your PC or car holder. I have neither of these things so I delete this.
Music.apk is the music player, and if your gonna replace it with another music player (Poweramp or Winamp for example) or simply dont want a music player, then is deletable.
MySketcher.apk is a touch drawing app which I dont use, so I delete that.
For me Titanium Backup PRO is a very useful program for uninstalling native .apks from the rom after install. Works perfectly.
If I forget to delete some native .apks I go into it, uninstall a load, then from the menu select -> more -> Clean up the Dalvik cache and it cleans up any stuff left that relate to the native .apks I have uninstalled.
There are many lists that can be found via google or here on XDA, but I have found many to be wrong. I worked out wot I could delete with trail and error.
Takes a while, but then you find out exactly what you can and cant ditch.
For sake, here is a list I have complied and have edited based on my knowledge of removing .apks prior to removal, some may or may not apply to you rom.
SHOULDNT REMOVE:
AccountAndSyncSettings.apk -> needed for Gmail Notifications
Calendar.apk -> Calendar
CalendarProvider.apk -> Calendar Provider
Camera.apk -> Camera
CertInstaller.apk -> Certificate Installer
Contacts.apk -> Contacts
Contacts.apk -> Contacts provider
DefaultContainerService.apk -> need to install apps
DownloadProvider.apk -> managed Downloads
DrmProvider.apk -> DRM provider
Fonts.apk -> system fonts
OmaDmcClient.apk -> OTA function can not simply be erased
Phone.apk -> Phone App
Settings.apk -> Settings App
SettingsProvider.apk -> Settings Provider
TelephonyProvider.apk -> Phone Provider
UserDictionaryProvider.apk -> Dictionary
Vending.apk -> Google Market
DeskClock.apk -> disables the alarm function
FmRadio.apk -> if the radio function is no longer needed
FmRadioProvider.apk -> if the radio function is no longer needed
GoogleCalenderSyncAdapter.apk -> Calendar Sync
GoogleContactsSyncAdapter.apk -> Sync Contacts
GoogleFeedback.apk
GoogleServicesFramework.apk -> provides account / login information for Google
CAN REMOVE
AnalogClockWidget.apk
AppAdvisor.apk
BatteryUsageWidget.apk
BookmarksWidget.apk
Browser.apk
Calculator.apk
CalendarWidget.apk
CarHome.apk
DeskClock.apk
DigitalClockWidget.apk
EmailWidget.apk
FriendsPlusWidget.apk
GalaxyWallpaper.apk
Gallery3D.apk
GenieWidget.apk
Gmail.apk
GoogleQuickSearchBox.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
Maps.apk
memo.apk
MessageWidget.apk
MusicWidget.apk
News.apk
PhotoAlbumWidget.apk
PhotoFrameWidget.apk
PolarisOffice.apk
VisualizationWallpapers.apk
VoiceSearch.apk
WeatherWidget.apk

nandroid first if unsure about removing a particular app - and you might have to turn off sig verification in recovery for install