Apps

[IngCr3at1on]

So my XDA account (that I almost never use) doesn't have enough posts to post on a dev board and I'm lazy. Because of that I'm opening this as an issue.

Looks like I'm not the only one that's been considering removing apps from the build (just I've been considering it on the build level lol)...

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

I'd like to remove several apps, not everything that others are removing (because some can be beneficial for easy TS or may be useful w/ headsets or if/when bluetooth is patched). The following is my proposed list:

Camera
CMStats
CMUpdateNotify
MMS
RomManager
Protips
VoiceDialer

The following are apps that others would probably remove but I am considering leaving for the listed reasons:

Browser (most people I believe are using silk; however if anyone decides to use voice search w/ a headset mic it will FC w/out this).
Contacts (easier contact navigation than other menus and required for phone.apk to functions)
Phone (can be used to access hidden menus [I'm not entirely certain of the presence of hidden menus on the KF but good to keep the ability for this I think, thoughts?])
Sound Recorder (can be used w/ a headset mic)

It's an easy removal but it would require forking the cyanogenmod vendor directory (which I'm more than willing to do) if doing that though I wonder if we couldn't break this repo into 2 (as separate entries) to pull everything from a repo manifest for syncing (again I would do this).

I'm considering doing the above anyway but I'm curious what yours or anyone else' thoughts may be.

[W0VOS]

Comments below...

On 1/15/12 1:10 AM, "IngCr3at1on"
<reply+i-2844906-5563c536b1cf802f9a5239eae23f51e243316459-1240788@reply.git
hub.com> wrote:

So my XDA account (that I almost never use) doesn't have enough posts to
post on a dev board and I'm lazy. Because of that I'm opening this as an
issue.

Been there. When I started this I was in the same boat.

Looks like I'm not the only one that's been considering removing apps
from the build (just I've been considering it on the build level lol)...

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

Yep, seems like a number of people have been trying (especially around the
phone stuff as it seems to consume some battery) but I've seen a lot of
issues with FC's when trying to do things in setup as the necessary files
are missing.

I'd like to remove several apps, not everything that others are removing
(because some can be beneficial for easy TS or may be useful w/ headsets
or if/when bluetooth is patched). The following is my proposed list:

Camera
CMStats
CMUpdateNotify
MMS
RomManager
Protips
VoiceDialer

I think the only thing you'd need to make sure is that none of these items
have a component in the setup stuff that could cause as issue. I haven't
done enough digging to know but it seems like as long as you stay away
from the phone stuff you'd likely be ok (that seems to be the only one
that's a bit intertwined into the setup stuff)

The following are apps that others would probably remove but I am
considering leaving for the listed reasons:

Browser (most people I believe are using silk; however if anyone decides
to use voice search w/ a headset mic it will FC w/out this).
Contacts (easier contact navigation than other menus and required for
phone.apk to functions)
Phone (can be used to access hidden menus [I'm not entirely certain of
the presence of hidden menus on the KF but good to keep the ability for
this I think, thoughts?])
Sound Recorder (can be used w/ a headset mic)

I'd keep those as well as they seem generally usable on the Kindle (and on
the phone I think you'll want it for the other reasons listed above)

It's an easy removal but it would require forking the cyanogenmod vendor
directory (which I'm more than willing to do) if doing that though I
wonder if we couldn't break this repo into 2 (as separate entries) to
pull everything from a repo manifest for syncing (again I would do this).

Not sure I follow the repo manifest part. If what you're proposing is to
create two repo's for the vendor stuff so that the person doing the build
can decide which files to pull depending on what they want (full ROM or
the modified ROM that doesn't include all the apps) then I'd say it's
doable but I'm not sure there is enough demand to warrant the work (given
that we could just branch the existing repo to account for the changes or
set up a new repo with the original as the parent so that any changes in
the parent could be reflected in the child but the child could still
substantially change the list of included apps.

I'm considering doing the above anyway but I'm curious what yours or
anyone else' thoughts may be.

---

Reply to this email directly or view it on GitHub:
#2

[IngCr3at1on]

Apps listed for removal are not required, reference : http://wiki.cyanogenmod.com/wiki/Barebones

Sorry no, I meant set up a manifest to sync all the repos for CM plus the blaze vendor and device repos directly into our build tree, than instead of syncing from the CM repo manifest we would sync from our own that pulled in all the CM repos as well as ours. Main issue is to do that we would have to break the Device and Vendor directories for the blaze into two separate repos. As for making 2 ROMs separate branches of the cyanogenmod vendor directory could do that as we could have to separate cyanogen_blaze make files, than again there should also be a way to add an option to build from 2 separate blaze make files in the same branch I just don't understand how to properly add a new device build to the tree for brunch/lunch options lol.

[IngCr3at1on]

OK, so I took another look at the vendor_cyanogen directory and it turns out not everything on my list can be removed from there. I'm not entirely certain where the other apps would be removed. Basically I've removed the CM support apps (rom manager, cm stats, cm update notifier). You can find that at the following:
https://github.com/IngCr3at1on/android_vendor_cyanogen

I was looking into the question regarding missing numbers on the keyboard, attempted pulling in the AOSP keyboard as well but it is also missing the numbers across the top... Oo

If you like you can sync from my manifest, this will pull the above listed vendor_cyanogen directory (it will however neglect all CM supported devices when you sync :D )

repo init -u git://github.com/IngCr3at1on/android.git -b gingerbread

Should be obvious anyway :D

This does not pull the KF directories you will have to continue to symlink those for now as you have been.