developing for the DSTL1 / N21

[crzyruski]

I want to try developing for the DSTL1 / N21

There are quite a few interesting things we can do...
Success has been been seen by xda-devs such as JesusFreke, Amon_RA, Haykuro, and Cyanogen (yes there others) in the field of Android ROMs. The ground work is there, porting and developing can commence.

Why do this?
Current ROM 1.5 - has many problems...
Unofficial ROM 1.6 (http://forum.xda-developers.com/showpost.php?p=4858841&postcount=47) - is a GREAT improvement, but makes one hungry for something better...

It would be awesome to have some success in this field. I know this device is capable of so much more, but I believe the implementation of the system is the issue. This is not the phone developers fault, as they have their own company agenda, but we could improve our own performance and satisfaction :).
For example, my device (1.6 rooted) lags with having only ~50% CPU utilization and ~50MB RAM free...
Overclocking (i mean forcing full CPU capacity - 624Mhz) the CPU has barely helped and only aided battery drain...

Relevant comparison of G1 vs DSTL1 (http://pdadb.net/index.php?m=pdacomparer&id1=1714&id2=1908) (N21) are
RAM - G1: 192MB vs DSTL1: 128MB
CPU - G1: 528Mhz vs DSTL1: 624Mhz

These specification comparisons say that G1 can run a better ROM than DSTL1? I don't think so. DSTL1 only loses in RAM, which can be made up for using swap (http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space)!

Devs had success with techniques using: App2SD (http://forum.xda-developers.com/showthread.php?t=512762), swap (http://forum.xda-developers.com/showthread.php?t=534714), ext3, and BFS (faster file system). I believe we could do something impressive here! There are pros and cons to this.

Developers and Testers would be needed. A team of 5 developers and a few testers should be able to get us on the right track. We would definitely need Linux experience, or the desire and ability to soak up all the info on Google ;)

A Linux kernel is a must for this phone, we would have to compile our own... It would be nice to preserve DUAL SIM, but in reality we might have to give up this luxury, as it is proprietary code, unless a new ROM is made backwards compatible (which is possible).

Cyanogen's Github is available for knowledge osmosis http://github.com/cyanogen

A DSTL1 Recovery by Amon_RA (based on Cyanogen's Recovery) is already in Beta...

Cool things are possible. Could I find some developers willing to donate their free time?
Please limit responses to dev talk.

[crzyruski]

reserved for later

[chrismotto]

crzyruski,
Believe it or not the very luxury you talk about giving up(dual sim) is the reason why may of us bother to buy these phones(DSTL1\N21) in the first place. Other wise we might as well go with a mainstream phone such as hero etc.

[crzyruski]

crzyruski,
Believe it or not the very luxury you talk about giving up(dual sim) is the reason why may of us bother to buy these phones(DSTL1\N21) in the first place. Other wise we might as well go with a mainstream phone such as hero etc.

Its a possibility that I'm not going to ignore, so I stated it.

The point is that the current OS is lacking. Initially we would want to port and learn from porting of the quality ROMs available now. Those obviously don't support dual-SIM.

Progress needs to start from somewhere. When someone releases a new port or ROM not all pieces work... look at the Eclair (2.0) port, half the features don't work!

If enough heads came together we could probably retain dual-SIM, common this is linux and I've seen the most amazing development come to realization. I just need the teamwork because it might take me a whole year in my spare time...

[sfabris]

Hi,

the most important IMHO is having a kernel working, built from sources.

Obviously, some closed source drivers must be rewritten, notably the NXP5209 (the GSM modem), if we want the device to be useful (i.e. if we want to make phone call).

My first attempt of booting with a custom kernel was unsucessfull (black screen), which brings to the second point: the lack of some sort of console for kernel debuging.

Any idea regarding the NXP? Anyone is aware of some opensource driver or specs?
Any idea also regarding kernel debugging in the N21/DSTL1?

sfabris

[crzyruski]

@sfabris
I will try to find info for the questions you have.
My initial work will be to make an emulator so we can test on PC and not our devices (because we need them functional for every day life :D)

Have you checked out how other modders have done kernel modifications?
Namely JF and Cyanogen?
I can't begin to comprehend so I'm glad you took the initiative with this.

Lets make some progress :)

[crzyruski]

Obviously, some closed source drivers must be rewritten, notably the NXP5209 (the GSM modem), if we want the device to be useful (i.e. if we want to make phone call).

Any idea regarding the NXP? Anyone is aware of some opensource driver or specs?


Maybe we have it all wrong???? Maybe its PNX?

PDA DB reports DSTL1 as having Nexperia PNX5209 (ARM946) Phone Controller.
http://pdadb.net/index.php?m=specs&id=1714&view=1&c=general_mobile_dstl1

A similar Android with this phone controller is WayteQ X-Phone (TechFaith Lancer)
http://pdadb.net/index.php?m=specs&id=1801&view=1&c=wayteq_x-phone_android_techfaith_lancer

[sfabris]

@sfabris
Have you checked out how other modders have done kernel modifications?
Namely JF and Cyanogen?
I can't begin to comprehend so I'm glad you took the initiative with this.

Lets make some progress :)

As I'm forced to HTC G1 until I'll wait the replacement for my N21 :mad: I'll go in detail on the kernel boot process on other hardware.

A fast way to test kernel in our every day device is kexec which should work also on ARM.

[crzyruski]

A fast way to test kernel in our every day device is kexec which should work also on ARM.

As far as I understand (http://en.wikipedia.org/wiki/Kexec), kexec is a program that can run a new kernel on the fly...
So I could try a new kernel right from my device without reflashing?
have you tried this? Or is this still theory?

[sfabris]

As far as I understand (http://en.wikipedia.org/wiki/Kexec), kexec is a program that can run a new kernel on the fly...
So I could try a new kernel right from my device without reflashing?
have you tried this? Or is this still theory?

I've tried it on x86, never on arm.
Support is there also for arm, but this not imply that also the Marvell PXA is supported.
It's basically the same way of booting Android from WM via haret.

Fastest way to boot your new kernel or to crash your machine:)

[crzyruski]

I have created an emulator.
FYI, LCD density should be 120.

Edit: Technically the density is 133...

[crzyruski]

I have been wrestling with the beta recovery-RA-DSTL1-v1.2.3
Amon_RA retrofitted his own recovery image to work for the DSTL1 (N21)...
IT HAS AWESOME POTENTIAL.
Currently ADB RECOVERY SHELL + ROOT is the only thing that is functional.

But I haven't been able to get in touch with him to continue work on it.

The following files prevent me from booting into RA's Recovery, so I remove them:
- e2fsck
- mke2fs
- parted
- tune2fs

Once I am in ADB RECOVERY SHELL I can push them back on ;) and do what I need to do.
Unfortunately the changes are persistent so if I were to reboot and try Recovery Mode again, it won't load :(

What is so special about those four programs that prevent my recovery from loading?????

[leventefarkas]

hi,
i'm just buy a sciphone n21 (actually is already in our office for 2 weeks but find it now:-( )
and i've to face myself in a situation that i can't use this phone:-( since i buy this phone because:
- i assume that google apps auto sync contact and calendars. unfortunately this phone has not google apps by default.
- and has dual sim support.

so my question: is there any way to upgrade it to a firmware which support is?

can i do anything to use my phone?

thanks in advance.
regards.

[andferno]

I have been wrestling with the beta recovery-RA-DSTL1-v1.2.3
Amon_RA retrofitted his own recovery image to work for the DSTL1 (N21)...
IT HAS AWESOME POTENTIAL.
Currently ADB RECOVERY SHELL + ROOT is the only thing that is functional.

But I haven't been able to get in touch with him to continue work on it.

The following files prevent me from booting into RA's Recovery, so I remove them:
- e2fsck
- mke2fs
- parted
- tune2fs

Once I am in ADB RECOVERY SHELL I can push them back on ;) and do what I need to do.
Unfortunately the changes are persistent so if I were to reboot and try Recovery Mode again, it won't load :(

What is so special about those four programs that prevent my recovery from loading?????

e2fsck is a filesystem check utility for ext2
mke2fs is for ext2 filesystem creation
parted is a partitioning tool
tune2fs is for change some filesystem parameters (usually checking interval)

I've read that recovery from Amon-Ra creates automatically 3 partitions (ext2, swap and FAT32). So those commands whould probably mean ext2 filesystem creation. I'm sure Amon-Ra could give us more information on this subject because he added them to the image.

Have you checked your SD card?.

PD: I'm waiting for my N21 :(. So I can't test yet.

[crzyruski]

e2fsck is a filesystem check utility for ext2
mke2fs is for ext2 filesystem creation
parted is a partitioning tool
tune2fs is for change some filesystem parameters (usually checking interval)

I've read that recovery from Amon-Ra creates automatically 3 partitions (ext2, swap and FAT32). So those commands whould probably mean ext2 filesystem creation. I'm sure Amon-Ra could give us more information on this subject because he added them to the image.

Have you checked your SD card?.

PD: I'm waiting for my N21 :(. So I can't test yet.

Thank you for that insight.
I am not sure what RA's recovery would have done on its own...
but I have initiated and completed successfully a partition of my SDCard that includes FAT32, swap, and ext2.
Now that I have done this, for experimentation really, I don't know how to use it and what it gives me.

Obviously the swap is useless because I would need a cooked Android ROM that would actually utilize swap.

ext2 is probably for apps2sd... which I tried unsuccessfully - probably because of my own mistake.

I will continue trying and report again later.

As far as Amon_RA, he mentioned he was working on upgrading all the recovery images he has put out to the next version - thus we will be in queue until this comes to pass. Maybe we can just skip this version and go to the next :)

[crzyruski]

I have completed the comparison of recovery images of the DSTL1 and N21.
For this test I used an original mtd2.img from my DSTL1 and an original mtd2.img from Slemmen's N21.

The recovery images are identical:

Both mt2.img are 4,194,304 bytes
Both mtd2.img-kernel are 2,141,616 bytes
Both mtd2.img-ramdisk.gz are 386,645 bytes


What is also interesting to note is that the two boot images i inspected were also identical.
The DSTL1 boot image is one that came with the 1502 update from General Mobile (which may or may not be identical to the original).

The original N21 boot image, thanks to ikarishinjisan, is identical to the DSTL1 boot image:

Both mt1.img are 4,194,304 bytes
Both mtd1.img-kernel are 2,141,816 bytes
Both mtd1.img-ramdisk.gz are 148,671 bytes


*Notice how both recovery and boot are the same size... must be padded?
*Notice how boot kernel is 200 bytes more than recovery kernel.... interesting...

On a side note:

Bootloader is identical as expected: both ikarishinjisan's and my mtd0.img are 1,048,576 bytes.

[dnfm]

If things are going to go custom, it might make some sense to put ext3 filesystems on these things.. ext3 is just ext2 with journalling, which could be helpful since phones can just die/get dropped/lose connection with battery/whatever.

[dnfm]

Also, this can be done with the tools already there..
mkfs.ext2
tune2fs -j

[crzyruski]

Also, this can be done with the tools already there..
mkfs.ext2
tune2fs -j

Are you referring to the Amon_RA's custom recovery?
I can't get tune2fs onto the recovery without trickery, definitely not noob friendly... until we figure out why.

But great suggestion :)
I'm guessing the ROM must be coded to make use of ext3, otherwise its worthless?

[dnfm]

The kernel would need to be configured to support ext3.

[crzyruski]

The kernel would need to be configured to support ext3.

A few of us are working on the kernel... it will definitely take time

[leventefarkas]

hi,
i'm able to root 1.6 onto my n21 and in this weekend i may have some time to play with my phone. so my questions:
- do you have the full copy of the original system, boot and recovery?
- do you have google maps for 1.6 (since it's missing from it)?
- how do you made the crzyruski-DSTL1_Donut_Test_rooted-v1.00.zip ? is there description about is?
- how do you made the crzyruski-DSTL1_Market_Patch-v1.10.zip? is there description about is?
- how does it working?
- which has the source?
- is there any technical howto, descriptions etc about android and n21? boot process, filesystem, kernel, kernel modules etc.
- what others working on and what is the current state.
- is this the best place discussion?
thanks in advance.

[crzyruski]

hi,
i'm able to root 1.6 onto my n21 and in this weekend i may have some time to play with my phone. so my questions:
- do you have the full copy of the original system, boot and recovery?
- do you have google maps for 1.6 (since it's missing from it)?
- how do you made the crzyruski-DSTL1_Donut_Test_rooted-v1.00.zip ? is there description about is?
- how do you made the crzyruski-DSTL1_Market_Patch-v1.10.zip? is there description about is?
- how does it working?
- which has the source?
- is there any technical howto, descriptions etc about android and n21? boot process, filesystem, kernel, kernel modules etc.
- what others working on and what is the current state.
- is this the best place discussion?
thanks in advance.

I'm sorry, most of your questions are off topic -please refer to the following places for better support and/or information
http://forum.xda-developers.com/showthread.php?t=565270
http://android-dls.com/wiki/index.php?title=DSTL1

Your development questions:
- ROM 1.6 + recovery 1.6 + google patch: none of these were developed here, they were only edited and shared here
- the kernel for this device is something we are trying to create - it is the most important part of this project, though certainly not the only part
- current state of kernel is in trial and error phase as we are essentially feeling our way in the dark
- we do not have source as of yet, we may need to build it from scratch using the public Android repo

If you are interested in developing, please catch up on all the info out there so far and begin to play with .img & .zip files available so far

[crzyruski]

the ROM zip file contains differences:

/data
data-update-post-script
/system
/app
/bin
/busybox
/etc
/fonts
/framework
/lib
/media
/usr
/xbin
build.prop
system-update-post-script
boot.img
update-validate-script

There is quite a bit of difference... Hopefully for the better. I just skimmed the surface.

Recovery ramdisk:

/data
/dev
/etc
/proc
/res
/sbin
/sys
/system
/tmp
default.prop
init
init.goldfish.rc
init.rc
init.yuhua.rc
init.yuhua.sh
initlogo.rle
modemon.sh
usb_ether_on.sh

Official Recovery kernel is larger by 2KB

The only two files in sbin are adbd and recovery, they are identical in file size, but are different when examined at the binary level.

BLUE means new files added
RED means difference

[andferno]

I was looking for differences between updates and found something funny. 1.6 Test kernel was compiled on 04/12/09 but has a previous version than 1.6 Official with date 01/12/09. May be a developing machine date error.

Framework directory is almost new. I think it and all Android apps were recompiled because GM generated some new apps to control dual sim.

Modules are new also. But binaries are almost the same. Only wifi and dual sim control are new.

[crzyruski]

I was looking for differences between updates and found something funny. 1.6 Test kernel was compiled on 04/12/09 but has a previous version than 1.6 Official with date 01/12/09. May be a developing machine date error.

Framework directory is almost new. I think it and all Android apps were recompiled because GM generated some new apps to control dual sim.

Modules are new also. But binaries are almost the same. Only wifi and dual sim control are new.

I noticed the same. I'm curious what the point of the data directory and the containing script is...

[crzyruski]

We use Sharp_lr388 LCD panel?

Seems to lag: Detect fast pull-down capacity(23,43)

I keep seeing this: mmc1: error -22 whilst initialising SDIO card

Camera is altek_5m

LCD density is 133

I would post my log dump but im not convinced I have cleaned it 200%

[andferno]

I noticed the same. I'm curious what the point of the data directory and the containing script is...

In first skim of files, I thought that it was to give rw permissions to users on all DATA filesystem. Ok, that's right, but why is it necessary if data was created by user?. May be they received some bug reports about no access to some files or directories and decided to put that script to prevent problems. I really don't know.

About data you got from your device, is very interesting to check component interfaces and try to get documentation or APIs to work with them. Thanks.

[wineleven]

I noticed the same. I'm curious what the point of the data directory and the containing script is...

It does nothing except formatting DATA.

You can just rm it from your image update package:)

[crzyruski]

@wineleven
Any ideas about this?

Official 1.6 has a message ringtone always plays "New Player" and its not even an option there. It doesn't matter what I change it to... it still plays this annoying ringtone when I get a new SMS, connect to USB, or any sort of notification. Its driving me NUTS!

12-05 03:38:34.219: DEBUG/NotificationService(78): Davis: useDefaultSound: false sound: null

Does anyone else have this problem or am I overlooking something???

[wineleven]

@wineleven
Any ideas about this?

1. Can we change the notification sound? I do not find a setting to personalize it:confused:

2. Maybe you can manual edit /system/build.prop.
ro.config.notification_sound=F1_New_SMS.ogg

[crzyruski]

1. Can we change the notification sound? I do not find a setting to personalize it:confused:

2. Maybe you can manual edit /system/build.prop.
ro.config.notification_sound=F1_New_SMS.ogg

You are right, I thought that "Message ringtone" was same as "notification ringtone", sorry.

The current build.prop says:
ro.config.sm_notification_snd=notf_gm_02.ogg
ro.config.sm_notification_snd_2=notf_gm_02.ogg
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.ringtone=GM_01.ogg
ro.config.ringtone_2=GM_01.ogg

But the current sound being played is "New Player.ogg"

Log dump says this:
12-05 04:28:25.917: DEBUG/NotificationService(78): Davis: useDefaultSound: false sound: content://settings/system/notification_sound
12-05 04:28:25.924: DEBUG/NotificationService(78): Davis: sound uri content://settings/system/notification_sound stream type 5

[wineleven]

Do you try a Factory reset?
It seems like some index error in content resolver database.

Uri "content://settings/system/notification_sound" should return ro.config.notification_sound F1_New_SMS.ogg fd rather than New Player.ogg at your phone.

You are right, I thought that "Message ringtone" was same as "notification ringtone", sorry.

The current build.prop says:
ro.config.sm_notification_snd=notf_gm_02.ogg
ro.config.sm_notification_snd_2=notf_gm_02.ogg
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.ringtone=GM_01.ogg
ro.config.ringtone_2=GM_01.ogg

But the current sound being played is "New Player.ogg"

Log dump says this:
12-05 04:28:25.917: DEBUG/NotificationService(78): Davis: useDefaultSound: false sound: content://settings/system/notification_sound
12-05 04:28:25.924: DEBUG/NotificationService(78): Davis: sound uri content://settings/system/notification_sound stream type 5

[crzyruski]

Do you try a Factory reset?
It seems like some index error in content resolver database.

Uri "content://settings/system/notification_sound" should return ro.config.notification_sound F1_New_SMS.ogg fd rather than New Player.ogg at your phone.

Probably stupid "MyBackup Pro"... I think it screwed up a lot of things on device when I did a FULL RESTORE onto Official 1.6 build 2485 from a FULL BACKUP Unofficial 1.6 :(

I will check back after I ROOT and flash build 2544! Thnx for your time :)

[crzyruski]

i made a diff but unfortunately they rebuild all apps and modules so everything seems to different, although the only real difference for me is the difference of default language from tr to en:-)
may be if i decode dex to jar to classes to java we can see the differences...

My went ahead and looked at Build 2485 vs Build 2544 as well as unofficial vs Build 2544

My findings are this:

Fixed default Turkish to English (leventefarkas already mentioned this)
Busybox was more complete on unofficial than Build 2485, so this was fixed in Build 2544 - but it looks like the missing pieces were just link files?
A few modules were fixed up. Specifically hci_uart.ko and libevdo-ril.so
A configuration script. Specifically sovold.conf
A few bins. Specifically wpa_supplicant and vold

[leventefarkas]

hi,
i'm just review crzyruski latest update and i like it mainly th new APNs list:-)
i've got a few questions:
- it seems you missed AlarmClock.odex from apps or is there any reason for this?
- it it intentional to remove email and filebrowser? i see you add k9mail and andexlopler, but why remove anything?
- your added apps has exec bit on in the zip although it's not a bug, it'd be nicer to chmod -x *
- you add GMaps which is neither Maps3.2.1-patched-no-root.apk nor Maps3.2.1-patched-root.apk anyway are you ssure these Maps3.2.1 are the real google maps? anyway why call it GMaps and not GoogleMaps as the original apps called (in mkt_mod_mod.zip) or from where did you get this apps?

i also look through CyanogenMod for other useful stuff like:
- like firstboot.sh
- /data/app/ : sam2, android-log-collector
- /system/app T-Mobile IM application, Amazon MP3 store
- init.d dir (also required for Apps2SD)
- and many scripts

[leventefarkas]

to somehow solve that no need for erase date and each installed extra apps (like google apps) before/after each update...

[crzyruski]

hi,
i'm just review crzyruski latest update and i like it mainly th new APNs list:-)
i've got a few questions:
- it seems you missed AlarmClock.odex from apps or is there any reason for this?
- it it intentional to remove email and filebrowser? i see you add k9mail and andexlopler, but why remove anything?
- your added apps has exec bit on in the zip although it's not a bug, it'd be nicer to chmod -x *
- you add GMaps which is neither Maps3.2.1-patched-no-root.apk nor Maps3.2.1-patched-root.apk anyway are you ssure these Maps3.2.1 are the real google maps? anyway why call it GMaps and not GoogleMaps as the original apps called (in mkt_mod_mod.zip) or from where did you get this apps?

i also look through CyanogenMod for other useful stuff like:
- like firstboot.sh
- /data/app/ : sam2, android-log-collector
- /system/app T-Mobile IM application, Amazon MP3 store
- init.d dir (also required for Apps2SD)
- and many scripts

- .odex files are class files for an apk. It is common practice to merge an odex files with its appropriate apk for easier management and space savings. I got AlarmClock from Cyanogen's ROM and all of his apks come odex-less.
- All apps included in a ROM cannot be uninstalled (easily), knowing this I wanted to replace certain apps that had better candidates available. I settled on a nice email client (k9) and a nice file explorer (AndExplorer)
-hmm, I will look into this chmod idea...
-Sorry, I did not claim to add the latest Google Maps, it is just a version of Google Map. In fact I leave this for the user upgrade at their leisure. This is the same Google Map I had released with a cupcake release some time back.
-firstboot.sh seems to run an audio loudness hack?
-sam2, I was considering providing this market alternative...
-do you think android-log-collector is worth it? T-Mobile IM application and Amazon MP3 store too? I never found much use for it personally and no one really asked.
-init.d dir is interesting, but I am not sure how it works yet... what invokes it?

Cyanogen's code is heavily modified, I burned myself a few times borrowing files left and right. If anyone wishes to piggy back on his code they should definitely do a lot of studying. I have much to catch up on, but too little time ;) on the bright side this latest release is pleasing to me and seems very stable and solid :)

[crzyruski]

to somehow solve that no need for erase date and each installed extra apps (like google apps) before/after each update...

its an interesting thing to look into to, so far I don't see it.

[leventefarkas]

- .odex files are class files for an apk. It is common practice to merge an odex files with its appropriate apk for easier management and space savings. I got AlarmClock from Cyanogen's ROM and all of his apks come odex-less.

but AlarmClock already in GM's rom so i there any reason why do you replace it with Cyanogen's version?

-firstboot.sh seems to run an audio loudness hack?

yes but we can learn from it...

-init.d dir is interesting, but I am not sure how it works yet... what invokes it?

this's the normal linux init.d dir and for app on sd it seems a must...

Cyanogen's code is heavily modified, I burned myself a few times borrowing files left and right. If anyone wishes to piggy back on his code they should definitely do a lot of studying. I have much to catch up on, but too little time ;) on the bright side this latest release is pleasing to me and seems very stable and solid :)

i'm also short of time but i'try to investigate it next week further...

[leventefarkas]

- .odex files are class files for an apk. It is common practice to merge an odex files with its appropriate apk for easier management and space savings. I got AlarmClock from Cyanogen's ROM and all of his apks come odex-less.

amyway from this:
http://groups.google.com/group/android-framework/browse_thread/thread/70ee61a240edc84a
it seems to me it'd be better to include it also...

[leventefarkas]

it'd be useful i you can tell us how did you do the rooted update?
- just unzip gm's update
- add su and Superuser
- remove Email, FileBrowser
- add a few addon from cm's update
- replace apns-conf.xml
- update build.prop and ystem-update-post-script
- and rezip it.
that's all or anything else?
thanks.

[hicazi45]

Hi
my phone general mobile dstl1. I want java midled manager but not stabil jvm. please help me. how will using jvm.
this application http://database.leakdroid.net/images-post/leakdroid/apps/java.zip
screen not support 240x400. thank you very much.

[leventefarkas]

it'd be useful to create one common page to collect all useful info about dstl1/n21. curently the "Rooting non-standard Android" and developing thread are long and there are amny info spread around but it;d be useful to collect all this information to one common page.

[hicazi45]

ok;) yes common page may be:)

[leventefarkas]

I got AlarmClock from Cyanogen's ROM

and is this AlarmClock better then the GM's version?

[crzyruski]

and is this AlarmClock better then the GM's version?

It is the same alarm clock everyone uses, except it has an Eclaire icon and smaller footprint

[crzyruski]

it'd be useful i you can tell us how did you do the rooted update?
- just unzip gm's update
- add su and Superuser
- remove Email, FileBrowser
- add a few addon from cm's update
- replace apns-conf.xml
- update build.prop and ystem-update-post-script
- and rezip it.
that's all or anything else?
thanks.

looks right to me

[crzyruski]

it'd be useful to create one common page to collect all useful info about dstl1/n21. curently the "Rooting non-standard Android" and developing thread are long and there are amny info spread around but it;d be useful to collect all this information to one common page.

There is a wiki, you should contribute :)

http://android-dls.com/wiki/index.php?title=DSTL1

there is also a centralized forum... http://www.androidspin.com/forum/index.php?f=75&rb_v=viewforum

[crzyruski]

amyway from this:
http://groups.google.com/group/android-framework/browse_thread/thread/70ee61a240edc84a
it seems to me it'd be better to include it also...

space on data partition is not very limited, especially when we move towards apps2sd. At this point we will have plenty of space on data partition. system partition space should be regarded important...

[crzyruski]

We are happy to have grown the DSTL1 / N21 community :)

Thank you all for participating. We have decided to continue support and discussions elsewhere.

We hope you continue to keep up with us on AndroidSpin's DSTL1 forum (http://www.androidspin.com/forum/index.php?f=75&rb_v=viewforum)! :)

[hilaireg]

Closed ... as per OP request.