yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Scrip:
call this systemapps.sh and place in the root of your zip

#!/bin/sh

grep -q trout /proc/cmdline && T=/sd-ext || T=/data
mount /system
mount $T
install -d $T/app_s
ln -sf $T/app_s /system/app

updater script

format SYSTEM:

run_program PACKAGE:systemapps.sh

copy_dir PACKAGE:system SYSTEM:

delete this block

format DATA:
copy_dir PACKAGE:data DATA:
symlink /data/app_s SYSTEM:app
set_perm 1000 1000 0771 DATA:app

or at least the format DATA: and symlink lines

now when you install on a trout (g1) everything that is in PACKAGE:system/app will end up in /sd-ext/app_s

if a magic (sapphire) /data/app_s

edit system/bin/a2sd

add

# mount and set perms
busybox mount -o rw,remount /
install -d /sd-ext
busybox mount -o r0,remount /

change all of the /system/sd to /sd-ext

or

make a second script that you use in your zip after install and before unmount system

#!/bin/sh
grep -q trout /proc/cmdline && \
ln -sf ../sd/app_s /system/app

but if I were you I would delete a2sd and fix the ramdisk's init.rc to use busybox's runparts and setup an init.d
[G1 Android Development] Scrip:
a diff

--- orig.uds
+++ new.uds
@@ -9,15 +9,12 @@
then
unmount("/data");
endif;
-format("MTD", "userdata");
format("MTD", "system");
mount("MTD", "system", "/system");
mount("MTD", "userdata", "/data");
package_extract_file("META-INF/com/bin/checksys.sh","/tmp/checksys.sh");
set_perm(0,0,755,"/tmp/checksys.sh");
run_program("/tmp/checksys.sh");
-ui_print("- Extracting System -");
-package_extract_dir("system", "/system");
ui_print("- Checking Device -");
if file_getprop("/tmp/nfo.prop","sysboard") == "trout" ||
file_getprop("/tmp/nfo.prop","sysboard") == "sapphire"
@@ -27,14 +24,12 @@
ui_print("- Device: HTC Dream -");
run_program("/sbin/mkdir","-p","/system/sd");
run_program("/sbin/mount","-t","auto","/dev/block/mmcblk0p2","/system/sd");
- package_extract_dir("sd-ext","/system/sd");
symlink("/system/sd/app_s","/system/app");
set_perm_recursive(1000, 1000, 0755, 0644, "/system/sd/app_s");
ui_print("- Installed to SD:EXT -");
else
# We have HTC Sapphire
ui_print("- Device: HTC Sapphire -");
- package_extract_dir("sd-ext","/data");
set_perm_recursive(1000, 1000, 0755, 0644, "/data/app_s");
symlink("/data/app_s","/system/app");
endif;
@@ -43,6 +38,8 @@
ui_print("Installer will bug!");
run_program("/sbin/exit","333");
endif;
+ui_print("- Extracting System -");
+package_extract_dir("system", "/system");

ui_print("- Symlinking Toolbox -");
symlink("toolbox", "/system/bin/getevent");

edit cleaner
[G1 Android Development] Rushness:
Sorry, but sometimes it's hard to understand what you mean. I can only see some "+" and some "-" and i dont really understand it^^
[G1 Android Development] Scrip:
it is a diff

created by the diff program

diff -ur orig new

- are lines which were removed

+ are lines which were added

example

- this line has an error
+ this line had an error

diff is line based

so changing has to had results in the above

@@ -16,26 +16,21 @@

is the offset

the original started at line 16 and ended at line 26

the new one starts at line 16 and ends at 21 (we made it shorter)

the lines which don't start with + or - are to give context

the patch program can apply a diff

it will use the offsets

if the file you are applying the patch to differs slightly to the original it may still be able to patch based on the context

using what is referred to as fuzzy logic
[G1 Android Development] Rushness:
So, i have to remove the lines with a "-" in front of them and i have to add the lines that are marked with a "+"?
[G1 Android Development] Infinimint:
Yes, the same way that you read commits on GitHub or other git hosting sites.
[G1 Android Development] AndDiSa:
you could also use a program called "patch" which will do it for you ...
[G1 Android Development] AndDiSa:
Looks to me as if there is a problem with the title_bar.xml, most likely due to a reference to an image which doesn't exist.
[G1 Android Development] Rushness:
Not really. If i modify the script to install as Sapphire version (everything on internal storage) then it boots up with no problem... So it seems that some files are missing.
[G1 Android Development] Infinimint:
Lol I didn't even look at the logcat... I'm just spitballin here, but...

Are you sure that your sdcard has an sd-ext partition? If it does, try wiping it or even reformating it.
[G1 Android Development] Rushness:
I'm pretty sure xD

I gonna try it... We'll see... But normally i should have one because i always had one..
[G1 Android Development] Scrip:
this is not something you flash

these are new files

move sd-ext/app_s to system/app

remove (or update) e2fsck or downgrade extfs on partition

most of the changes are to init.rc

--- init.rc.orig
+++ init.rc.new
@@ -13,7 +13,8 @@
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
# export PHONE_STORAGE /emmc
- export SD_EXT_DIRECTORY /system/sd
+ export SD_EXT_DIRECTORY /sd-ext
+ export DOWNLOAD_CACHE /cache/download
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar

# gpu permissions
@@ -32,6 +33,7 @@
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
+ mkdir /sd-ext 0771 system system
mkdir /config 0500 root root
mkdir /sqlite_stmt_journals 01777 root root
mount tmpfs tmpfs /sqlite_stmt_journals size=4m
@@ -70,8 +72,8 @@
mount yaffs2 mtd@system /system
mount yaffs2 mtd@system /system ro remount noatime

-# import /system/init.rc
-# trigger system
+ import /system/init.rc
+ trigger system

# We chown/chmod /data again so because mount is run as root + defaults
mount yaffs2 mtd@userdata /data nosuid nodev noatime
@@ -81,6 +83,7 @@
# Mount compressed filesystems
mount squashfs loop@/system/lib/modules/modules.sqf /system/lib/modules ro
mount squashfs loop@/system/xbin/xbin.sqf /system/xbin ro
+ mount squashfs loop@/system/fonts/fonts.sqf /system/fonts ro

# Create dump dir and collect dumps.
# Do this before we mount cache so eventually we can use cache for
@@ -286,13 +289,22 @@
setprop net.tcp.buffersize.gprs 4092,8760,11680,4096,8760,11680
# setprop net.tcp.buffersize.wimax 4096,87380,110208,4096,16384,110208

- start a2sd
- start swap
+ start adbd
+
+ # start init.d script support
+# exec /system/bin/sysinit
+# exec appear broken
+ start sysinit

+on property:sysinit.done=1
class_start default

## Daemon processes to be run by init.
##
+service sysinit /system/bin/sh /system/bin/sysinit
+ disabled
+ oneshot
+
service console /system/bin/sh
console

@@ -384,10 +396,6 @@
service installd /system/bin/installd
socket installd stream 600 system system

-# no
-#service flash_recovery /system/etc/install-recovery.sh
-# oneshot
-
service racoon /system/bin/racoon
socket racoon stream 600 system system
# racoon will setuid to vpn after getting necessary resources.
@@ -412,19 +420,6 @@
disabled
oneshot

-# Execute files in /etc/init.d before booting
-service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
- disabled
- oneshot
-
-service a2sd /system/bin/sh /system/bin/a2sd
- disabled
- oneshot
-
-service swap /system/bin/logwrapper /system/bin/sh /system/bin/swap
- disabled
- oneshot
-
# Clean shutdown
service reboot /system/bin/shutdown -r
disabled
[G1 Android Development] :
I cheap added service "init.d", "a2sd", and "swap" because sysinit (tried putting it in /sbin and in /system/bin/) it wouldn't start for some reason.. i checked the permissions in updater-script and they seemed right.. i'll just send a version with apps on /data.. Looking through your comments, that's probably why :)

BTW, the actual mountpoint is /system/sd, not sd-ext because of the a2sd script i use.. It's legacy.. I should really update my scripts lol
[G1 Android Development] Scrip:
I removed them because they didn't work

I fixed it

BTW, it is now sd-ext not /system/sd

I also fixed the updater script

it did very stupid things like format data and system only to then go on and tell the user that their phone wasn't compatible

it had some dumb sed hatchet job screwing with the build.prop

just have 3 .props

build.prop

build.trout.prop

build.sapphire.prop

make a diff to see what I did
[G1 Android Development] :
lol, running the services individually worked for me, but running sysinit with exec didn't, but I guess it should work now...

When I tried to getprop ro.product.device (when I had build.trout.prop and build.sapphire.prop) , it seemed to not detect the correct device?
[G1 Android Development] Scrip:
it would be very easy to update your as2d script to sd-ext

sed -i 's@/system/sd@/sd-ext/g' /system/bin/a2sd

but just drop this in init.d (chmod o+x)

#!/system/bin/sh
# a very simple a2sdext script by Scrip 2012-03-19
for i in install mv mount grep;do
alias $i="busybox $i"
done
a2sdext(){
#fix links
test -L /data/app && rm /data/app && install -d -m 771 -o 1000 -g 1000 /data/app
install -dv -m 771 -o 1000 -g 1000 /sd-ext/app
busybox mv -v /data/app/* /sd-ext/app/ 2> /dev/null
busybox mount -o bind /sd-ext/app /data/app/
}
grep -q sd-ext /proc/mounts && a2sdext

if you want to have dalvik-cache on sd-ext as well

#!/system/bin/sh
# a very simple a2sdext script by Scrip 2012-03-19
for i in install mv mount grep;do
alias $i="busybox $i"
done
a2sdext(){
#fix links
test -L /data/$1 && rm /data/$1 && install -d -m 771 -o 1000 -g 1000 /data/$1
install -dv -m 771 -o 1000 -g 1000 /sd-ext/$1
busybox mv -v /data/$1/* /sd-ext/$1/ 2> /dev/null
busybox mount -o bind /sd-ext/$1 /data/$1
}
grep -q sd-ext /proc/mounts && \
for i in app dalvik-cache;do
a2sdext $i
done
[G1 Android Development] Rushness:
Nice Scrip, you always know a solution - perfect! :)

I will try the new stuff and give feedback in like 20 minutes.
[G1 Android Development] :
nevermind #
[G1 Android Development] Rushness:
What...? o.o
[G1 Android Development] :
Sorry, I mean to say that a2sd only worked on eclair if I ran it after vold (hence creating a2sd service seperately from sysinit)
[G1 Android Development] Rushness:
I was talking with zFr3eak about the whole topic and he also said that it would be a better idea to put just everything on data/app_s, but my question is: How much space will you have for apps from the market, etc.?
[G1 Android Development] Scrip:
vold has nothing to do with it

unless you are using vold to mount your ext partition

since sysinit is mounting /sd-ext before it runs a2sd it will work

that is unless someone sticks a useless old e2fsck in which fails to check ext3/4

delete e2fsck you don't need it

or you could

adb remount
adb shell sed -i s/e2fsk_exitcode=../e2fsk_exitcode=0/ system/etc/init.d/05mountsd

and skip the check

---------- Post added at 01:02 AM ---------- Previous post was at 12:47 AM ----------

all you have to do is mount sd-ext

ok let us save some time

I will upload a working version

when I say working I use the term loosely

it runs slow

has no useful features

fc's a lot

why you guys would want to use this rom is beyond me

but here it is

http://dl.dropbox.com/u/67521906/Fixed_rush_legendary_sense_v0.9.3_Signed.zip

I have been flashing ezterry's ezgb-2636-v1.5.2_S.zip over it

the changes are in the ramdisk and ezterry's kernel installer extracts that
[G1 Android Development] Scrip:
Working e2fsck

working e2fsck
[G1 Android Development] Rushness:
I gonna try it now... Normaly this ROM is not forceclosing anything. But since i sent it to e334 and use his version as a base even the Magic install force closes so much stuff on my phone, i cant even unlock my SIM Card. But i think that is caused due the low internal storage. I hope we can fix everything.
[G1 Android Development] Rushness:
Okay, it's not working again... Same logcat output. Is this a problem with MY phone are does anyone tested this on his phone?
[G1 Android Development] Rushness:
Maybe, e334, could you make a new version?

Just use the ROM i sent you earlier and integrate only a wifi fix and your modified kernel. And then we can like "start from scratch".
[G1 Android Development] Scrip:
It still runs like glass

but at least Settings doesn't fc

If you still have problems with sd-ext then check if sd-ext is mounted

(df)

if it isn't then run

sh -vx /system/etc/init.d/05mountsd | tee /data/sdextlog.txt

added a few features

Fixed_rush_legendary_sense_v0.9.5_Signed.zip

Changelog

in no particular order

updated update-binary

The old one didn't format MTD correctly

Added Ezterry's zram compcache scripts

to use it, as root do

setprop persist.zram.size X
setprop persist.service.swappiness Y

where X is the size of compcache in MB and Y is swappiness (0-100)

Added a x2sdex init.d service

To configure see /sd-ext/.x2sdex

Fixed Settings FC (bad pngcrush script?)

Fixed run-parts init.d service

You have to get init to wait until run-parts has done its thing

and run-parts requires PATH environment else it will hang forever..

removed a2sd and swap init services

added working e2fs utils

auto locate system apps

If system size is 132 MB or more (cmtd) system apps will install on system

If system < 132 MB and device is a Dream system apps will install to /sd-ext

If system < 132 MB and device is a Sapphire system apps will install to /data

Added AutoCMTD

Added assert checks (device/hboot/copy fail)

removed build.prop hacks from updater-script (separate build props for devices now)

squished fonts

I think that is everything
[G1 Android Development] Rushness:
Scrip, are you testing the ROM on a Dream or on a Sapphire?
[G1 Android Development] Scrip:
Dream

but that should make no difference

the error you were getting was because android hit a dead symlink

either the symlink was just wrong or sd-ext was not mounted

there was a mess with e2sfck I assume taken from some recovery but it had missing libs

I replaced with e2fs utils with the ones compiled from cm7 src

it should just work

if not then something is wrong

running 05mountsd with -vx will print each script line as it executes (-v) and show the expansion (-x) of those commands
[G1 Android Development] Rushness:
Yeah, that's why i was asking, i'm also testing on the Dream and the previous versions were just acting strange. I will try this on like 20:00 GMT+1 time because i'm still in school till 19:00 o'clock. Hopefully we got a working release this time, also working with my weird HTC Dream :)
[G1 Android Development] Rushness:
Still the same error... Even when executed that:

sh -vx /system/etc/init.d/05mountsd | tee /data/sdextlog.txt

Any idea? :/
[G1 Android Development] Scrip:
post /data/sdextlog.txt so I can read it
[G1 Android Development] Rushness:
I'm unsure about this but Droid Explorer does not show ANY file in there... o.o
[G1 Android Development] Scrip:
if you can't give me anything to read there is not much I can do
[G1 Android Development] Rushness:
But what am i supposed to do if there is just no file in there?^^

I mean, i flashed the ROM, let it boot until that error and startet your command with adb shell... I could give you the text that opens up in my cmd.

C:\>adb shell
# sh -vx /system/etc/init.d/05mountsd | tee /data/sdextlog.txt
sh -vx /system/etc/init.d/05mountsd | tee /data/sdextlog.txt
#!/system/bin/sh
#
# mount ext partition from sd card
set -v
+ set -v
set -x
+ set -x

BB="logwrapper busybox";
+ BB=logwrapper busybox

if [ "$SD_EXT_DIRECTORY" = "" ];
then
SD_EXT_DIRECTORY=/sd-ext;
fi;
+ [ /sd-ext = ]

# find SD Card
for MMC_NUM in `seq 0 9`;
do
MMC_TYPE=`cat /sys/block/mmcblk$MMC_NUM/device/type`
if [ "$MMC_TYPE" = "SD" ];
then
# 2nd partition of sdcard should be the sd-ext if exist
SD_EXT_PART=/dev/block/mmcblk${MMC_NUM}p2
break
fi
done
+ seq 0 9
+ cat /sys/block/mmcblk0/device/type
+ MMC_TYPE=SD
+ [ SD = SD ]
+ SD_EXT_PART=/dev/block/mmcblk0p2
+ break

if [ -b "$SD_EXT_PART" ];
then
log -p i -t mountsd "Checking filesystems..";

# fsck the sdcard filesystem first
if [ -x `which e2fsck` ];
then
e2fsck -y $SD_EXT_PART
e2fsk_exitcode=$?
else
echo "executable e2fsck not found, assuming no filesystem errors"
e2fsk_exitcode=0
fi

# set property with exit code in case an error occurs
setprop cm.e2fsck.errors $e2fsk_exitcode;
if [ "$e2fsk_exitcode" -lt 2 ];
then
# mount and set perms
$BB mount -o noatime,nodiratime,barrier=1 -t ext3 $SD_EXT_PART $SD_EXT_D
IRECTORY;
if [ "$?" = 0 ];
then
$BB chown 1000:1000 $SD_EXT_DIRECTORY;
$BB chmod 771 $SD_EXT_DIRECTORY;
log -p i -t mountsd "$SD_EXT_DIRECTORY successfully mounted";
else
log -p e -t mountsd "Unable to mount filesystem for $SD_EXT_DIRECTOR
Y!";
fi
else
log -p e -t mountsd "Unable to repair filesystem, disabling apps2sd";
fi
fi
+ [ -b /dev/block/mmcblk0p2 ]
+ log -p i -t mountsd Checking filesystems..
+ which e2fsck
+ [ -x /system/xbin/e2fsck ]
+ e2fsck -y /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p2e2fsck: is mounted. Cannot continue, aborting.

+ e2fsk_exitcode=8
+ setprop cm.e2fsck.errors 8
+ [ 8 -lt 2 ]
+ log -p e -t mountsd Unable to repair filesystem, disabling apps2sd
#
[G1 Android Development] Scrip:
Yes that is what I was after

Note to self

cm's mount script exports e2fsck exit code as a prop

getprop cm.e2fsck.errors

is quicker :)
​

Well the words say sd-ext is already mounted

but

you had issues

if I do the same I get the words but exitcode 0

exitcode 8 is something else http://linux.die.net/man/8/e2fsck

I'm assuming sd-ext is not mounted?

what to do you get from df?

df

if sd-ext is mounted

what the heck do it anyway

ls -l /system /sd-ext

other options (which may be easier)

try a different sdcard

reformat you current sdcard

going back to my note to myself

you could try rebooting and then

getprop cm.e2fsck.errors

it could be that sd-ext didn't mount the first time, but did the second/third+ times and we are getting a slightly false reading here

I don't think it is the rom

as it has been working fine for me (anyone to back me up on that?)

link is Fixed_rush_legendary_sense_v0.9.5_Signed.zip

details a few posts up
[G1 Android Development] Rushness:
Okay so i got good and bad news.. :D

First off the good news:

I was able to do all the commands and stuff with my OLD(!!!) sd card.

df:

Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 55984 0 55984 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 93184 88128 5056 95% /system
/dev/block/mtdblock5 93952 19716 74236 21% /data
/dev/block/loop0 512 512 0 100% /system/lib/modules
/dev/block/loop1 768 768 0 100% /system/xbin
/dev/block/loop2 2816 2816 0 100% /system/fonts
/dev/block/mtdblock4 27648 1192 26456 4% /cache
/dev/block/mmcblk0p2 468331 8228 435118 2% /sd-ext
/dev/block/mmcblk0p2 468331 8228 435118 2% /cache/download

ls:

# ls -l /system /sd-ext
ls -l /system /sd-ext
/sd-ext:
drwxrwx--x 2 1000 2001 1024 Mar 23 22:12 download

/system:
lrwxrwxrwx 1 0 0 13 Mar 23 22:10 app -> /sd-ext/app_s
drwxr-xr-x 1 0 2000 2048 Mar 23 22:10 bin
-rw-r--r-- 1 0 0 4073 Aug 1 2008 build.prop
-rw-r--r-- 1 0 0 206 Aug 1 2008 build.sapphire.prop
-rw-r--r-- 1 0 0 239 Mar 23 22:12 build.trout.prop
drwxr-xr-x 1 0 0 2048 Mar 23 22:10 customize
drwxr-xr-x 1 0 0 2048 Mar 23 22:11 etc
drwxrwxrwx 2 0 0 256 Mar 22 20:33 fonts
drwxr-xr-x 1 0 0 2048 Mar 23 22:10 framework
drwxr-xr-x 1 0 0 2048 Mar 23 22:10 lib
drwxr-xr-x 1 0 0 2048 Mar 23 22:10 lost+found
drwxr-xr-x 1 0 0 2048 Mar 23 22:10 media
drwxr-xr-x 1 0 0 2048 Mar 23 22:10 usr
drwxrwxrwx 2 0 0 4785 Mar 21 06:04 xbin
#

getprop:

# getprop cm.e2fsck.errors
getprop cm.e2fsck.errors
0
#

So i tried a NEW(!!!) sd card, reformated it, etc...

now the installer atleast puts in the folder structure. With my OLD(!!!) sd card there wasn't any file in some folder.

But the data/app/ folder is still empty.

Here is a picture of the NEW(!!!) sd card structure:

Bad news are that i'm still getting the same error... Possibly because i dont have any folder/data in the actual data folder...

In data/app there is not a single file.

Any idea?
[G1 Android Development] Scrip:
why are you expecting anything to be in data/app?

system/app is pointing to /sd-ext/app_s

which is correct

but

/sd-ext/app is missing

so it looks like recovery did not mount /sd-ext and the system apps were sent to ramfs

what recovery are you using?

ra 1.7 and cwr 2.5.0.7 should both work correctly

check /sd-ext exists in recovery

ls /

if not then create it

mkdir /sd-ext

try mounting sd-ext before flashing

mount /sd-ext

if that fails

mount -t auto /dev/block/mmcblk0p2 /sd-ext

or replace

run_program("/sbin/mount","/sd-ext");

with

run_program("/sbin/mount","-t","auto","/dev/block/mmcblk0p2","/sd-ext");
[G1 Android Development] Rushness:
Magic happend.. :D

The final solution was just that tiny bit of a command:

mount /sd-ext

It installed flawless and booted up with no problems.

But i miss something, the HTC Widgets haven't been installed. o.o

And the free available space on internal storage is only 41,49MB. //i was guessing something like 89MB like on SenseLX.

Although those problems, thanks Scrip, for everything!!!

Could you tell me the line that i have to put into the updater-script so it mounts the sd-ext before flashing everything?
[G1 Android Development] Scrip:
that is what is so strange

it should be doing that already

then
if file_getprop("/tmp/nfo.prop","sysboard") == "trout"
then
ui_print("- Device: HTC Dream -");
run_program("/sbin/mount","/sd-ext");

that is the exact same command :confused:

I can add a little loop to the above, effectively waiting until it is confirmed mounted

breaking out of that loop after 10sec
​

space

45mb of apps means a lot of dalvik-cache

edit

89mb free means you must have been using sd-ext for everything

so comment out each line in .x2sdex or

echo app app-private dalvik-cache data >> /sd-ext/.x2sdex

might be easier
​

/sd-ext/.x2sdex

uncomment dalvik-cache and/or data

it will then use /sd-ext

you don't have to reboot

sh /system/etc/init.d/10x2sdex

not as easy to undo

in recovery edit the .x2sdex file and comment or delete them

then move the files back to data/

example for moving data files back

mv /sd-ext/data/* /data/data/
mv /sd-ext/system/* /data/system/

yes data is special, two folders
[G1 Android Development] Scrip:
I reverted the apks to the ones in 9.2.1

add back Rosie.apk and HtcAddProgramWidget.apk (from 9.3)

these are the ones I reverted

system/framework/framework-res.apk
system/app/FieldTest.apk
system/app/NetworkLocation.apk
system/app/Rosie.apk
system/app/GoogleCheckin.apk
system/app/HtcAddProgramWidget.apk
system/app/GoogleSubscribedFeedsProvider.apk

it was probably just the framework-res.apk that was an issue

try one by one
[G1 Android Development] Rushness:
Okay i'll try all the stuff... Right now it's like 12md here in Germany... And today is saturday so i'm not quite sure how much stuff i can test today, because i have a lot of stuff to do... :/

But i will test the stuff atleast tomorrow.
[G1 Android Development] tass0s:
when the next is out, will it work on 32A too??
[G1 Android Development] Rushness:
Propably not, for now.
[G1 Android Development] Rushness:
code.google.com mirror added.
[G1 Android Development] AndyFox2011:
Hey dude,

I flashed this ROM this morning after deciding to use my old G1 again, but it stuck at the boot animation for about 15mins then just switched off :(

Yes i do have my SD Card partitioned, and i did use the superwipe, anything else i missed?
[G1 Android Development] frankdrey:
When did this become a full blown Sense? O_o

Didn't it used to be a themed version of a regular ROM?

If so, you need to stop screwing with the name :S It's very confusing.

Anyway, /me will try this as soon as possible :D

Then once I'll get a new batter (old one lasts 10 min w/o charger), Ill use it as my everyday ROM if it's good.
[G1 Android Development] Infinimint:
It's always been a Legend Sense port haha maybe you're thinking of GinSense or FroSense ;)
[G1 Android Development] hootnath:
me too