yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] cursordroid:
I'm quite sure this app already exists...

http://www.androlib.com/android.application.com-riteshsahu-apnbackuprestore-qAwz.aspx
[myTouch 3G, Magic Android Development] ralle.gade:
thank you for helping

hey dudes thanks for the help i have searched myself but just couldn't find anything :D i really love this comunity great ppl in here!!
[myTouch 3G, Magic Android Development] ralle.gade:
this also works to all hero ROM's right? :D just wanna be shure
[myTouch 3G, Magic Android Development] tazz9690:
yes it does work on hero
[myTouch 3G, Magic Android Development] sitimber:
also do it with your wifi wep keys

adb pull /data/misc/wifi/wpa_supplicant.conf C:\

adb push C:\wpa_supplicant.conf /data/misc/wifi
[Hero CDMA General] goku14238:
Hey guys, just a little side note.. I posted a video on how I rooted the the Hero, with the steps described here, on youtube.. I went to phandroid to get my daily does of android news and it was linked on their site.. Makes me really happy.. First video ever.. :cool:

Just a side note guys..

Video is dedicated to all the hard working guys/and gals that have been working to hack the Hero. You made it possible.

Good job to everyone, we achieved what many people said would be impossible. Im proud, of all of you
[Touch HD Themes and Apps] antoniomistretta:
For download:

http://rapidshare.com/files/305596049/Anto..._Icone_nere.cab
[Touch HD Themes and Apps] eighty1:
Nice. Where can clock be downloaded? Thanks
[Touch HD Themes and Apps] antoniomistretta:
http://xdaforums.com/showthread.php?t=581866
[Touch HD Themes and Apps] eighty1:
Thank You.
[General Questions and Answers] buffalosolja42:
Hello Forum fam a good friend of mine is traveling to UK for the entire month of Dec, he asked me if I knew f any prepaid services there that could allow just data (not unlimited but enought to tweet and email some). He doesn't mind paying something that would have him covered during his stay. Anyone have any suggestions please let me know so I can get back with him. He asked and I said I know people (ie you guys) that can point him in the right direction. Thanks in advanced.
[General Questions and Answers] stylez:
I use O2 network on pre-pay top up £15 and get unlimited text & unlimited internet for a month.

If not applicable as don't know if need to have specific sim "since been on network for while so just changed tariff" you can top up £10 get 300 texts and 250MB costs £7.50 as bolt on

http://freesim.o2.co.uk/nvBtjrmP

Hope that helps.
[General Questions and Answers] buffalosolja42:
thanks1!!

!!!!!!!I appreciate it.
[Touch Pro2, Tilt 2 Windows Mobile General] grant9908:
fallow the link for detailed installation of pocketnesterplus which will let you play NES in landscape mode :D

http://www.howardforums.com/showthread.php?threadid=1006997
[Touch Pro2, Tilt 2 Windows Mobile General] SlimJ87D:
How well does it work? What FPS do you get for the average game? If it's like 12 then it's not really worth it =/

But if it's above 24 then count me in!

EDIT: I think you meant a NES emulator... not SNES...
[Touch Pro2, Tilt 2 Windows Mobile General] Hanson68:
I'm confused -- it this for NES or SNES games or both? It appears to be for NES games.
[Touch Pro2, Tilt 2 Windows Mobile General] grant9908:
What are you guys talking about!?!? it clearly says NES XD!!! (I edited lol)
[Touch Pro2, Tilt 2 Windows Mobile General] SlimJ87D:
It is a NES emulator. I don't know if there are any good NES games worth playing lol.

SNES would be awesome.
[Touch Pro2, Tilt 2 Windows Mobile General] grant9908:
hmmmm, I have no clue what this is or what it means, can you please explain so I can be in the loop?
[Touch Pro2, Tilt 2 Windows Mobile General] grant9908:
also......here is a link to a pocket SNES

http://freewareppc.com/download/utilities/pocketsnes.shtml
[Touch Pro2, Tilt 2 Windows Mobile General] SlimJ87D:
Oh it means frame rate per second.

So how choppy the game is. The human eye can hardly tell the difference in 24FPS and 30FPS is good. 60FPS being the best.
[Touch Pro2, Tilt 2 Windows Mobile General] grant9908:
it only runs at about 15 to 25 right now, but there is a new version coming out that has been leaked all over the net that will allow you to play any game balls to the wall. everything 60+
[Touch Pro2, Tilt 2 Windows Mobile General] aldamon:
The NES has tons of good ROMs. The problem I have with TP2 NES emulation (I use Smartgear) is the spacing of the buttons. They're too far apart for fast reactions in games like Mike Tyson's Punch-Out. I miss the 5-way on my Treo 650.
[Touch Pro, Fuze General] jpiano:
I have an HTC Fuze (Touch Pro) running on AT&T's network. I am using SPB Mobile Shell 3.5.1 instead of TouchFlo. When making or receiving a phone call, once the call disconnects or I hang up my phone freezes! No response to button presses or screen taps, just frozen. This lasts anywhere from 5 to 15 seconds before it releases everything back to normal. Any thoughts out there???
[Touch Pro, Fuze General] Cassetti:
What Rom are you running? The stock original rom?

2 suggestions:

1) If you are incessant about not upgrading your ROM to something a bit more colorful, faster, Do a hard reset (BACK UP ALL DATA AND SETTINGS TO EXTERNAL DRIVE) by holding the volume up and the center button on the front of your phone, and then insert your stylus into the reset button on the bottom (i find holding the phone power-button into your gut works best for keeping the phone stable) - keep holding unil the reset to factory defaults screen comes up.

2) Flash your phone to a much better ROM and enjoy a better way of life. (I'm all about the energy roms, but many people swear by others)
[Touch Pro, Fuze General] jpiano:
Thanks for the tip. I'm actually running the latest official stock rom the HTC released a five or six months ago, for AT&T WM 6.1. Maybe I'll give another ROM a try sometime.
[Touch Pro, Fuze General] bluespire:
It's probably Mobile Shell. It seems to have some bugs. For instance, when I am done with a call, it sometimes it just hangs on the screen where you can choose which number to call for someone. I have to go into the Task Manager and kill it, which doesn't kill the entire program, just that window. I'm so annoyed by it, that I am probably going to get rid of it.

I'm running energy ROM, if it matters (don't remember which version).
[Touch Pro, Fuze General] mputtr:
it can also be your radio. When I was originally flashing radios, I found out that some give me stronger signals, but it crashes my phone right after the call. look into that as well.
[Android Software Development] 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 - 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 (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!

Devs had success with techniques using: App2SD, swap, 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.
[Android Software Development] crzyruski:
reserved for later
[Android Software Development] 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.
[Android Software Development] crzyruski:
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...
[Android Software Development] sfabris:
Having a kernel working

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
[Android Software Development] 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 :)
[Android Software Development] crzyruski:
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
[Android Software Development] sfabris:
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.
[Android Software Development] crzyruski:
As far as I understand, 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?
[Android Software Development] sfabris:
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:)
[Android Software Development] crzyruski:
I have created an emulator.

FYI, LCD density should be 120.

Edit: Technically the density is 133...
[Android Software Development] crzyruski:
files prevent recovery-RA-DSTL1-v1.2.3 from loading

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?????
[Android Software Development] leventefarkas:
is there any ways to update the firmware of N21

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.
[Android Software Development] andferno:
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.
[Android Software Development] crzyruski:
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 :)
[Android Software Development] crzyruski:
N21 vs DSTL1: stock comparisons

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.
[Android Software Development] 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.
[Android Software Development] dnfm:
Also, this can be done with the tools already there..

mkfs.ext2

tune2fs -j
[Android Software Development] crzyruski:
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?
[Android Software Development] dnfm:
The kernel would need to be configured to support ext3.
[Android Software Development] crzyruski:
A few of us are working on the kernel... it will definitely take time
[Android Software Development] leventefarkas:
start to do something

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.
[Android Software Development] crzyruski:
I'm sorry, most of your questions are off topic -please refer to the following places for better support and/or information

http://xdaforums.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
[Android Software Development] crzyruski:
official vs unofficial: donut package review

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
[Android Software Development] andferno:
Differences

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.
[Android Software Development] crzyruski:
I noticed the same. I'm curious what the point of the data directory and the containing script is...
[Android Software Development] crzyruski:
log dump info

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%
[Android Software Development] andferno:
Yes, me too...

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.
[Android Software Development] wineleven:
It does nothing except formatting DATA.

You can just rm it from your image update package:)
[Android Software Development] crzyruski:
Notification Sound

@wineleven

Any ideas about this?
[Android Software Development] wineleven:
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
[Android Software Development] crzyruski:
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
[Android Software Development] 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.
[Android Software Development] crzyruski:
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 :)
[Android Software Development] crzyruski:
Official 1.6: Build 2485 vs Build 2544

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