Galaxo tweaks - get more memory :)

kam187 · October 23rd, 2009, 11:12 PM

# Remount read/write
adb remount

# open shell
adb shell

# go to apps directory
cd /data/app_s

# delete QuickDroid (if you want to)
rm QuickDroid.apk

# delete NPS sync (it doesn't work so why run it!)
rm wssyncmlnps.apk

# disable drexe (this gets baseband info for NPS. Who needs it!)
mv /system/bin/drexe /system/bin/drexe.off

# disable npsmobex (this handles auth with nps)
mv /system/bin/npsmobex /system/bin/npsmobex.off

Now kill any running apps, and flush the cache to get a good baseline of free memory:

sync ; echo 3 > /proc/sys/vm/drop_caches ; cat /proc/meminfo ; free

I get this Total memory after boot with all tasks killed:

Code:

MemTotal:        95948 kB
MemFree:         23308 kB
Buffers:            44 kB
Cached:          15392 kB

a total of (23308 + 15392)/1024 = 37.79296875

You need to add the MemFree and Cached to get the total free memory usable by apps. This is the MAX memory you will have with no apps running (if u run the sync etc line above). The sync line above is usefull to compare the REAL memory change when you use various widgets or programs.

Extra info..

sync - flushes any disk caches

echo 3 > /proc/sys/vm/drop_caches - Free pagecache, dentries and inodes:

cat /proc/meminfo - Get memory and cache usage

free - get memory usage

kam187 · October 23rd, 2009, 11:22 PM

If you don't use the SDK to take screenshots or debug then you can also kill debuggerd:

mv /system/bin/debuggerd /system/bin/debuggerd.off

Remember you can undo all the mv's by moving the .off file back to the original name

Code:

MemTotal:        95948 kB
MemFree:         29268 kB
Buffers:            44 kB
Cached:          13728 kB

Total memory = (29268 + 13728)/1024 = 41.98828125 mb

My clean process list:

Code:

  PID  PPID USER     STAT   VSZ %MEM CPU %CPU COMMAND
# my top command
 1594  1525 0        R     2064  2.1   0 14.2 top
 
# ESSENTIAL PROCESS - core System process
 1085  1018 1000     S     158m169.1   0  0.0 system_server
 
# ESSENTIAL PROCESS - android core process
 1129  1018 10000    S     122m130.1   0  0.0 android.process.acore
 
# ESSENTIAL PROCESS - handles auto sync, and google connections
 1153  1018 10012    S     105m112.8   0  0.0 com.google.process.gapps
 
# ESSENTIAL PROCESS - keyboard and locale
 1198  1018 10000    S     103m110.3   0  0.0 com.android.inputmethod.latin
 
# ESSENTIAL PROCESS - handles phone functions
 1127  1018 1001     S     101m108.4   0  0.0 com.android.phone
 
# ESSENTIAL PROCESS - handles android media (technically you could kill this 
                      but you'll cripple the phone media functions!)
 1245  1018 10013    S    93184 96.9   0  0.0 android.process.media
 
# USEFULL PROCESS - Handles alarm clock and events.  You could kill it to 
                    save 1mb max, but its not really worth it.
 1285  1018 10059    S    92128 95.8   0  0.0 com.android.alarmclock
 
# ESSENTIAL PROCESS - system process, handles forking requests
 1018     1 0        S    71300 74.2   0  0.0 zygote /bin/app_process -Xzygote /
 
# ESSENTIAL PROCESS - Handles media player, camera etc.  Also the headset 
                      keys for music get intercepted by this process
 1019     1 1013     S    22696 23.6   0  0.0 /system/bin/mediaserver
 
# ESSENTIAL PROCESS - API between OS and modem
 1017     1 1001     S     9568  9.9   0  0.0 /system/bin/rild
 
# USEFULL PROCESS - Allows adb.  You could kill it, but you wouldnt be 
                    able to shell in anymore!
 1023     1 0        S     3332  3.4   0  0.0 /sbin/adbd
 
# ESSENTIAL PROCESS - allows one to one comms between apps,
 1020     1 1002     S     1168  1.2   0  0.0 /system/bin/dbus-daemon --system -
 
# ESSENTIAL PROCESS - handles disks
 1011     1 0        S      868  0.9   0  0.0 /system/bin/vold
 
# ESSENTIAL PROCESS - handles running services
 1010     1 1000     S      808  0.8   0  0.0 /system/bin/servicemanager
 
# ESSENTIAL PROCESS - handles apk installation and removal.  You need it 
                      if you use market!
 1021     1 0        S      800  0.8   0  0.0 /system/bin/installd
 
# USEFULL PROCESS - handles auto rotate - uses very little memory anyway
 1013     1 0        S      256  0.2   0  0.0 /system/bin/akmd2

Vap1d- · October 23rd, 2009, 11:38 PM

Thanks Kam, good stuff. Will have to do this on my other computer that has adb on it tomorrow.

pegasus21 · October 24th, 2009, 12:36 AM

On a side note, do you notice if your phone stays awake more on this custom rom as opposed to official or maybe it's just something I installed recently

During a 2hr period, my phone is running for about 6-7mins of the time. Trying to see what might have caused the running period.

kam187 · October 24th, 2009, 12:50 AM

I havnt checked because i've been fiddling with the OS too much. Once i get this stable i'll have a look

Andronix · October 24th, 2009, 01:12 AM

Pegasus, yeah I noticed that also, try removing taskiller, it likes keeping the phone awake. I removed lot of things from original GalaxHero to know exactly wuat was the cause.

Kam, thanks for that, very good info, as usual.

kam187 · October 24th, 2009, 01:55 AM

ok so here's a quick script file to delete loads of unused stuff like diagnostics. Thanks Pegasus21

It deletes the HTC keyboard (not the default one that's used in galaxo or galaxoHero which is a skinned android one).

It deletes Java and ext4 support. You can edit what it deletes if you want to keep them.

It deletes galaxoapps, which lets face it is pretty useless after the first install

It deletes NPS processes because we'll never update this ROM using NPS.

It removes QuickDroid because it wastes CPU indexing. Install it from market again, or edit the file if u like it.

It deletes the debuggerd process, if you use the SDK you might want to keep that. (adb will always work tho)

To use, download the zip and put it into the same directory as adb. Then open a command prompt:

# mount read/write
adb remount

# upload the script
adb push clearapps.sh /system/clearapps.sh

# Open a shell
adb shell

# make the script executable
chmod +x /system/clearapps.sh

# run the script
/system/clearapps.sh

# reboot
reboot

----

Then after you have rebooted, use taskkiller to kill any left over processes and you can check your ram with:

sync ; echo 3 > /proc/sys/vm/drop_caches ; cat /proc/meminfo ; free

kam187 · October 24th, 2009, 02:26 AM

Galaxo Hero:

Code:

MemTotal:        95948 kB
MemFree:         29268 kB
Buffers:            44 kB
Cached:          13728 kB

Total memory = (29268 + 13728)/1024 = 41.98828125 mb

Galaxo:

Code:

MemTotal:        95948 kB
MemFree:         20076 kB
Buffers:            44 kB
Cached:          27204 kB

Total memory = (20076 + 27204)/1024 = 46.171875mb

There's only about 5mb between them :-/

pegasus21 · October 24th, 2009, 02:47 AM

Definitely not a task killer since I disabled it with pm just to see...
Not handcent sms either...

Quite odd but at least I managed to isolate the 4% drop in battery to a few items.

Andronix · October 24th, 2009, 03:46 AM

you may find usefull "autostarts".

intouch · October 24th, 2009, 05:28 AM

Quote:

Originally Posted by pegasus21

During a 2hr period, my phone is running for about 6-7mins of the time. Trying to see what might have caused the running period.

Mine is worse.
With II5 firmware, my Galaxy is running for about 12 mins in a 1hr period!
I thought it was normal.
I have WiFi and 3g data enabled. No third-parties applications installed.

Andronix · October 24th, 2009, 05:58 AM

Uh, I'd suggest factory reset and monitor things for a bit.

Rastaman-FB · October 24th, 2009, 03:27 PM

Quote:

Originally Posted by intouch

Mine is worse.
With II5 firmware, my Galaxy is running for about 12 mins in a 1hr period!
I thought it was normal.
I have WiFi and 3g data enabled. No third-parties applications installed.

Are you using the case

kam187 · October 24th, 2009, 03:58 PM

Experimenting with stock II5 now... stay tuned...

MemTotal: 95976 kB
MemFree: 30788 kB
Buffers: 44 kB
Cached: 22452 kB

Total 51.992mb

Seems pretty stable at just over 50mb free

intouch · October 25th, 2009, 02:33 AM

Quote:

Originally Posted by Rastaman-FB

Are you using the case

No, I'm not using the case!

boomtopper · October 25th, 2009, 08:59 AM

Quote:

Originally Posted by kam187

Experimenting with stock II5 now... stay tuned...

MemTotal: 95976 kB
MemFree: 30788 kB
Buffers: 44 kB
Cached: 22452 kB

Total 51.992mb

Seems pretty stable at just over 50mb free

Hi Kam have you done a script aswell for cleaning up the stock II5?

hippy · October 25th, 2009, 03:06 PM

The script posted by kam187. I know some of these items are self-explanatory, but before I remove them any chance you could explain some of the odd ones in case I actually want to keep them? eg. would I ever use debuggerd? DebugTool.apk? What's Jbed.apk? Is LogCollector useful? No need for FTP client or VPB connections? What's bootsetttings? Why remove camerafirmware? CSC? CurrentDataState? You get the idea

I'm just wondering what a lot of this does and why you would choose to remove it (obv. forgetting the memory bonus).

Thanks!

Quote:

#!/system/bin/bash

# disable drexe (this gets baseband info for NPS. Who needs it!)
mv /system/bin/drexe /system/bin/drexe.off

# disable npsmobex (this handles auth with nps)
mv /system/bin/npsmobex /system/bin/npsmobex.off

mv /system/bin/debuggerd /system/bin/debuggerd.off

rm -rf /data/app_s/DebugTool.apk

rm -rf /data/app_s/galaxoapps.apk

rm -rf /data/app_s/HDBlog.apk

rm -rf /data/app_s/Jbed.apk

rm -rf /data/app_s/Logcollector.apk

rm -rf /data/app_s/Quickdroid.apk

rm -rf /data/app_s/SwiFTP_1.11.apk

rm -rf /data/app_s/VPN_Connections_v09.apk

rm -rf /data/app_s/HTC_IME.apk

rm -rf /data/app_s/bootsetting.apk
rm -rf /data/app_s/bootsetting.odex

rm -rf /data/app_s/CameraFirmware.apk
rm -rf /data/app_s/CameraFirmware.odex

rm -rf /data/app_s/CSC.apk
rm -rf /data/app_s/CSC.odex

rm -rf /data/app_s/CurrentDataState.apk
rm -rf /data/app_s/CurrentDataState.odex

rm -rf /data/app_s/DataCopy.apk
rm -rf /data/app_s/DataCopy.odex

rm -rf /data/app_s/FactoryTest.apk
rm -rf /data/app_s/FactoryTest.odex

rm -rf /data/app_s/FileCopy.apk
rm -rf /data/app_s/FileCopy.odex

rm -rf /data/app_s/FileCount.apk
rm -rf /data/app_s/FileCount.odex

rm -rf /data/app_s/InputEventApp.apk
rm -rf /data/app_s/InputEventApp.odex

rm -rf /data/app_s/lcdtest.apk
rm -rf /data/app_s/lcdtest.odex

# rm -rf MusicService.apk

rm -rf /data/app_s/PhoneErrService.apk
rm -rf /data/app_s/PhoneErrService.odex

rm -rf /data/app_s/RilFactoryApp.apk
rm -rf /data/app_s/RilFactoryApp.odex

rm -rf /data/app_s/serviceModeApp.apk
rm -rf /data/app_s/serviceModeApp.odex

rm -rf /data/app_s/shutdown.apk
rm -rf /data/app_s/shutdown.odex

rm -rf /data/app_s/Switchers.apk
rm -rf /data/app_s/Switchers.odex

rm -rf /data/app_s/testgps.apk
rm -rf /data/app_s/testgps.odex

rm -rf /data/app_s/TSPFirmware.apk
rm -rf /data/app_s/TSPFirmware.odex

rm -rf /data/app_s/WlanTest.apk
rm -rf /data/app_s/WlanTest.odex

rm -rf /data/app_s/wssyncmlnps.apk
rm -rf /data/app_s/wssyncmlnps.odex

rm -rf /system/lib/libjbedvm.so

# rm -rf lib\libpdfreader.so - Used by htc's pdfreader

rm -rf /system/lib/ext4dev.ko

rm -rf /system/lib/jbd2.ko

shanyel · October 25th, 2009, 05:17 PM

can someone get here the Samsung Switchers.apk? mistakenly i deleted it
thanks,

kam187 · October 25th, 2009, 08:08 PM

Stock script i just did quickly. I just changed the directorys etc.

You'll get some file not found stuff because i didnt remove all the lines for files that are only in the Galaxo Hero rom

You'll probably need busybox. Install the custom recovery if u dont have it already and 'enable su'.

Then boot into normal mode and copy busbox and the script to your sdcard. Then adb shell

# superuser (superuser.apk will load on the phone, allow it)
su

# remount system read/write
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system

# copy busy box
cat /sdcard/busybox > /system/bin/busybox

# change permisions
chmod 4755 /system/bin/busybox

# install busy box
/system/bin/busybox --install -s /system/bin/

# fix cp
cd /system/bin
busybox cp -s busybox cp

# copy script to system (there's no +x on the sdcard)
cp /sdcard/clearappsstock.sh /system
chmod 744 /system/clearappsstock.sh

# run it, and ignore the file not found stuff
/system/clearappsstock.sh

Then reboot, adb shell back in, su and type ps and look for the debuggerd process. If its not there everything went ok

Hippy:

debuggerd - Its only used if you develop apps with the SDK. You won't need it. If you do develop apps you'll probably need to restore to factory and make sure you're stuff works on a stock phone anyway.

DebugTool.apk - its some debug menu u can bring up. You'll never use it!

Jbed.apk - Java. I dont need or use it. You can keep it if you want

LogCollector - Used to collect crash logs etc. You dont really care about crashlogs

bootsetttings - switches boot settings i think. Once the firmware has booted first time it wont be used again

camerafirmware - used to update the camera firmware. Pretty dangerous (see the other thread). After first boot you'll never use this again.

CSC - CSC inits for first boot. Not used again

CurrentDataState - I forget what this one is tbh!

MEGAUPLOAD - The leading online storage and file delivery service

Andronix · October 26th, 2009, 12:44 PM

I ran your script and changed compcache settings to 64000 so compcache can use all free RAM. It works quite well sofar. Browser now rarely clean open tabs and phone is not crawling after some time. Try it...

drakaz · October 26th, 2009, 03:33 PM

And another great job from kam187 !!

Currently working on a light version of the rom (the new Galaxo), with this kind of purification, a lightest kernel and a few init.rc tunning. I hope this futur rom will be fastest. kam187, if you have another improvment...

skandalfo · October 26th, 2009, 03:49 PM

Please don't remove development facilities from your roms.

I actually love GalaxoHero, but it would be a hassle having to search and re-install the debugging features after a rom installation / upgrade. Debugging in the device is much better than using the emulator (at least for me). It's better leaving the option to enable it in (if that's not what the "Settings / Applications / Development / USB Debugging" option does).

One thing is removing items that don't work at all and that you can't disable (NPS sync thingies), and another one is removing things that actually work.

kam187 · October 26th, 2009, 03:58 PM

USB debugging enables adb.

The device itself runs adbd and debuggerd, these are different processes for different purposed. adbd handles adb shell etc, so is usefull to keep running. Otherwise you'll be really stuck if something broke!

debuggerd is used by the SDK debugger. It shows debug information for your test process. Unless you're developing apps you dont need it. And if you do one day, just adb in and rename it from debuggerd.off back to debuggerd

If you're developing apps you should be running a stock system anyway!

so debuggerd is useless for most users, and those that need it should know not to run that line

hippy · October 26th, 2009, 04:02 PM

Surely it's better to distribute the lightest ROM and leave it up to users to install stuff?

Also, there's going to be far fewer users that needing development tools than not, so it makes sense to remove them and let users that need them add them later.

scollie · October 27th, 2009, 01:01 PM

Kam in post #7 you included a script clearapps.zip which deletes files from
/data/app_s.

Then in post #19 you included a link to a MEGAUPLOAD file clearappsstock.zip which deletes files from
/system/app

So I am now a bit confused, should I run one or both of these scripts?

Also in #19 you have the following lines
cp /sdcard/clearappsstock.sh /system
chmod 744 /system/clearapps.sh

# run it, and ignore the file not found stuff
/system/clearapps.sh

which seem to copy the appsstock file but executes the apps one, is there a typo here?

kam187 · October 27th, 2009, 01:36 PM

Yup typos!

If you have any Galaxo rom you ONLY need to run clearapps.sh and not install busybox etc:

# mount read/write - remount work on galaxo, but not stock
adb remount

# upload the script - you can upload directory to /system, OR copy to sdcard and copy upto you

# push clearapps.sh from adb folder to the phone
adb push clearapps.sh /system/clearapps.sh
# Open a shell
abd shell

OR

# Open a shell
abd shell
# copy clear apps from the sdcard to system
cp /sdcard/clearapps.sh /system

# make the script executable
chmod +x /system/clearapps.sh

# run the script
/system/clearapps.sh

# reboot
reboot

If you have any stock rom you need to:
- enable SU from recovery
- install busybox
- run clearappsstock.sh

And so follow post 19 exactly (http://androidforums.com/samsung-i7500/12365-galaxo-tweaks-get-more-memory.html#post71842)

scollie · October 27th, 2009, 02:14 PM

Thanks for the quick reply, your help is really appreciated!
While you are around, maybe you could help re the control characters that appear when I use a cmd terminal as shown here

C:\Documents and Settings\Stan>cd ../../temp/windows

C:\TEMP\windows>adb remount
remount succeeded

C:\TEMP\windows>adb shell
____ _
/ ___| __ _| | __ ___ ___ _
| | _ / _` | |/ _` \ \/ / | | |
| |_| | (_| | | (_| |> <| |_| |
\____|\__,_|_|\__,_/_/\_\\__, |
|___/ ..... by drakaz

←[01;32m[root@galaxy←[01;31m:←[01;34m/]←[00m ls
ls
←[1;34mcache←[0m ←[1;32minit←[0m ←[1;34msbin←[0
m
←[1;34mdata←[0m ←[1;32minit.goldfish.rc←[0m ←[1;34msdcard←
[0m
←[1;34mdbdata←[0m ←[1;32minit.rc←[0m ←[1;34msqlite_
stmt_journals←[0m
←[0;0mdefault.prop←[0m ←[0;0mlogo.rle←[0m ←[1;34msys←[0m
←[1;34mdev←[0m ←[1;34mproc←[0m ←[1;34msystem←
[0m
←[1;36metc←[0m ←[1;34mroot←[0m ←[1;34muserdat
a←[0m
←[01;32m[root@galaxy←[01;31m:←[01;34m/]←[00m
←[01;32m[root@galaxy←[01;31m:←[01;34m/]←[00m su
su
# ls
ls
←[1;34mcache←[0m ←[1;32minit←[0m ←[1;34msbin←[0
m
←[1;34mdata←[0m ←[1;32minit.goldfish.rc←[0m ←[1;34msdcard←
[0m
←[1;34mdbdata←[0m ←[1;32minit.rc←[0m ←[1;34msqlite_
stmt_journals←[0m
←[0;0mdefault.prop←[0m ←[0;0mlogo.rle←[0m ←[1;34msys←[0m
←[1;34mdev←[0m ←[1;34mproc←[0m ←[1;34msystem←
[0m
←[1;36metc←[0m ←[1;34mroot←[0m ←[1;34muserdat
a←[0m
#

Sorry for the formatting above but I'm not sure how else to copy from the cmd window (I 'marked' the text then copied it).
I've highlighted in bold the 2 'ls' commands and the 'su' command but as the output is surrounded by control chars it is difficult to read it!

Thanks for any help you can give with this. If you have any queries it will be tomorrow before I can get back to you as I am off out for the evening now!

kam187 · October 27th, 2009, 05:17 PM

Yeah those are anoying for us windows users! The best thing to do is use putty to a redicrected local port.

I'm sure, like me, you dont like to keep ssh running all the time, nor wifi, so do this:

- Turn on ssh in galaxoconfig and reboot - this will generate the ssh keys
- Turn off ssh in galaxoconfig and reboot.

You only need to do that once and never again.

Now make two .bat files in the adb tools directory:

SSH_ON.bat and put this inside it:

adb forward tcp:9999 tcp:2222
adb shell "/system/xbin/dropbear -E -A -N root -U 0 -G 0 -C password -p 2222"

and also SSH_OFF.bat and put this inside it
adb shell "kill `ps | grep dropbear | awk '{print $1}'`"

You can change 'password' to anything you like. The SSH_OFF just finds the dropbear pid and kills it.

After running SSH_ON just putty to 127.0.0.1 and port 9999, make sure to select ssh as the protocol. And hey presto a nice colour shell, and stuff like vim also works!

As soon as you're in type bash to switch to bash shell, and get history to work.

So save a profile in putty, and every time you want to connect, double click SSH_ON, and the windows will stay open showing u ssh connections. Use putty to connect.

When you're done run SSH_OFF, and the SSH_ON windows should dissapear as dropbear was killed.

kam187 · October 28th, 2009, 02:11 AM

Drakaz, it seems you can steal some memory from the GPU

This is the dream 10mb kernel hack:

You need to edit \BSP\kernel_2.6.27\arch\arm\mach-msm\board-saphire.c

Around Line 1140

if (smi_sz == 32) {
mi->bank[0].size = (84*1024*1024);
} else if (smi_sz == 64) {
mi->bank[0].size = (101*1024*1024);
} else {
printk(KERN_ERR "can not get smi size\n");

Change '(101*1024*1024);' to 0x06d00000, which is 108mb. We can probably go even higher i think.

You also need to change this line to the same value \BSP\kernel_2.6.27\arch\arm\mach-msm\board-saphire.h

#define SMI64_MSM_LINUX_BASE MSM_EBI_BASE
#define SMI64_MSM_LINUX_SIZE 0x06500000

---------

Now check out \BSP\kernel_2.6.27\arch\arm\mach-msm\board-init.c

Samsung even left a few comments lol:

Code:

#define MSM_EBI_BASE  0x10000000
#define MSM_EBI_SIZE  0x06D00000    // Total 109M for ARM11
#ifdef CONFIG_MSM7K_SMI64
#define SMI64_MSM_PMEM_MDP_BASE 0x02000000
#define SMI64_MSM_PMEM_MDP_SIZE 0x00800000  // 8M
#define SMI64_MSM_PMEM_ADSP_BASE    0x02800000
#define SMI64_MSM_PMEM_ADSP_SIZE  0x00D00000  // 13M-->7M from IF4 => 8M for MPEG4 Play 480*360 ==> 13M for safety
#define SMI64_MSM_PMEM_CAMERA_BASE 0x03500000
#define SMI64_MSM_PMEM_CAMERA_SIZE 0x00B00000  // 11M
#endif
#define MSM_PMEM_MDP_SIZE 0x800000
#define MSM_PMEM_CAMERA_SIZE 0xa00000
#define MSM_PMEM_ADSP_SIZE 0xd00000
#define MSM_PMEM_GPU1_SIZE 0x800000
#define MSM_FB_SIZE  0x100000     // 1M is enough for Orion Project

kam187 · October 28th, 2009, 03:09 AM

Hmm did i get this right.. I think the misterious extra 10mb that appeared in the 'H' firmwares is from extra memory stolen from the GPU. Thats why all the 3D stuff broke :-/

Wow, well done samsung lol

z0mbi3 · October 28th, 2009, 05:39 AM

Quote:

Originally Posted by kam187

Hmm did i get this right.. I think the misterious extra 10mb that appeared in the 'H' firmwares is from extra memory stolen from the GPU. Thats why all the 3D stuff broke :-/

Wow, well done samsung lol

I thought 3D was broken in all firmwares?

kam187 · October 28th, 2009, 01:24 PM

I read some stuff worked on G firmwares and it all broke on H firmwares. Maybe i got it wrong. Anyway looks like drakaz is building the mods in and a tiny kernel! Should be niceeee

Andronix · October 28th, 2009, 05:24 PM

We need to sticky thread with drakaz' custom rom. He definately deserved it.

kam187 · October 29th, 2009, 01:21 AM

Yeah. We should probably get a active galaxy member here to moderate and handle things like that for us.

z0mbi3 · October 29th, 2009, 10:30 AM

Quote:

Originally Posted by kam187

Yeah. We should probably get a active galaxy member here to moderate and handle things like that for us.

Off you go then

Andronix · October 29th, 2009, 12:22 PM

Quote:

Originally Posted by z0mbi3

Off you go then

i'll second that

kam187 · October 29th, 2009, 05:58 PM

lol ok then, if u insist!

TimK · October 29th, 2009, 06:45 PM

Kam187, can you clarify something?

Do I need to leave apps like GMail running in order to get push notifications of new E-mails, or is the GApps process enough?

How does this work with other apps that notify, like Messaging (well, I actually use chompSMS) and Twitter apps (I use Swift)? Do they have to be running in order for notifications to work?

I ask because my battery life is considerably worse with Galaxo than it was with the stock II5 firmware. I'm thinking that killing some of these processes will help battery life as well as making the phone faster.

Thanks,
Tim

kam187 · October 29th, 2009, 06:59 PM

Gmail, messaging, google maps, calender and a few other procresses run at boot because google think you'll use them all the time. Ok messaging, yeah, but the rest i dont thing i do!

The OS actually handles the events, and launches the associated app when you click on the notification. So if an SMS came in, when you click it, it'll open it in your registered SMS app.

The app itself doesnt need to be running since it doesnt handle the events, only displays the data associated to it, like an SMS.

The only exception is gapps which is needed for autosync.

Alarmclock is another interesting one. It eats 2mb of ram doing pretty much not alot!
It needs to be run at boot to schedule your set alarms with the OS. Then it can be killed. When the scheduled alarm is triggered in the OS, it opens alarmclock app to handle it - and make the alarm noise etc.
So this can also be killed after boot if you like.

Calender works the same, it must be run once to schedule your calender events.

With both alarmclock and calender, if you open then to change an event, it will reschedule with the OS, and so you can kill it again if you like.

You can download 'autostarts' from the market to check whats autostarting and turn stuff off. Its not free i think.

Just remember leave alarmclock and calender autostart on and kill them after boot. alarmclock is actually a system task so is hidden in taskiller

kam187 · October 29th, 2009, 07:58 PM

BTW..

On II8 with NPS processes removed, and only the google search widget and normal clock, after killing all tasks in taskiller after boot I have 47mb free.

With the flip clock with weather widget I have 40mb free

kam187 · October 29th, 2009, 08:26 PM

Once all your apps are setup, and you're pretty close to your final system, you can delete the dalvik cache and force it to regenerate all the dex files.
[You need root. Boot the phone, adb shell in then.. ]

cd /data/dalvik-cache
rm *
reboot

The phone will reboot, and take a little longer to boot. You'll probably gain about 1mb of RAM.

dalvik cache? - All apps get translated into bytecode that gets fed to the Dalvik virtual machine. Its a bit like a Java VM with .jar files. When new apps appear, or cache files are missing for them, the dalvik VM converts all apps into their .dex equivalent. It checks all dependancies and creates the best set of .dex files it can.

If you installed/removed loads of stuff, or like most of us, installed loads of apps, the cache may not be optimal. Remember sometimes it will include libraries inside the .dex files. Dalvik is supposed to redo the caches for any files that might be affected by install/uninstall or library update, but it doesnt seem to do a good job!

Andronix · October 30th, 2009, 02:03 AM

Another classical FAQ post, thx kam: )

Btw how do I register app that I moved to app_s? Would clearing dalvik cache do?

pegasus21 · October 30th, 2009, 02:05 AM

Register? Normally on a boot up, the dalvikvm does it's magic and app_s is symbolically linked from /system/app so it's included during boot up too.

Andronix · October 30th, 2009, 02:12 AM

Quote:

Originally Posted by pegasus21

Register? Normally on a boot up, the dalvikvm does it's magic and app_s is symbolically linked from /system/app so it's included during boot up too.

All apps from market are by default installed in small system partition. app_s folder is not on that partition.

pegasus21 · October 30th, 2009, 02:38 AM

I don't get what you're getting at.

Andronix · October 30th, 2009, 02:54 AM

Quote:

Originally Posted by pegasus21

I don't get what you're getting at.

ahh never mind

[root@galaxy:/data]cd /system
[root@galaxy:/system]ls -la | grep app
lrwxrwxrwx 1 0 0 11 Oct 19 08:13 app -> /data/app_s
[root@galaxy:/system]

kam187 · October 30th, 2009, 03:50 AM

The dalvik cache is 'all' programs converted into .dex files. So any programs your phone see's in its app paths, OR tries to run, will get the treatment and cached in that directory

So there's no need to worry about anything else, just delete the cache as above.

scollie · October 30th, 2009, 11:47 AM

Quote:

Originally Posted by kam187

Yeah those are anoying for us windows users! The best thing to do is use putty to a redicrected local port.

I'm sure, like me, you dont like to keep ssh running all the time, nor wifi, so do this:

- Turn on ssh in galaxoconfig and reboot - this will generate the ssh keys
- Turn off ssh in galaxoconfig and reboot.

You only need to do that once and never again.

Now make two .bat files in the adb tools directory:

SSH_ON.bat and put this inside it:

adb forward tcp:9999 tcp:2222
adb shell "/system/xbin/dropbear -E -A -N root -U 0 -G 0 -C password -p 2222"

and also SSH_OFF.bat and put this inside it
adb shell "kill `ps | grep dropbear | awk '{print $1}'`"

You can change 'password' to anything you like. The SSH_OFF just finds the dropbear pid and kills it.

After running SSH_ON just putty to 127.0.0.1 and port 9999, make sure to select ssh as the protocol. And hey presto a nice colour shell, and stuff like vim also works!

As soon as you're in type bash to switch to bash shell, and get history to work.

So save a profile in putty, and every time you want to connect, double click SSH_ON, and the windows will stay open showing u ssh connections. Use putty to connect.

When you're done run SSH_OFF, and the SSH_ON windows should dissapear as dropbear was killed.

Just had a chance to try the above. Thanks very much for that! Using putty is so much better than the wiindows cmd terminal.

Cheers!!

gnasher666 · October 30th, 2009, 10:13 PM

Hi, I can't find my app_s directory. When I cd into data then do an ls I get nothing back and if I cd into /data/app_s I get an error stating can't cd to app_s My phone is working properly and I have the Galaxo Hero rom installed. Any ideas please? Thanks.

Quote:

Originally Posted by kam187

# Remount read/write
adb remount

# open shell
adb shell

# go to apps directory
cd /data/app_s

kam187 · October 30th, 2009, 10:27 PM

Are you in recovery or normal boot?

You need to be booting normally and then adb in.