yashsingh1/xdaforums huggingface dataset:
[MDA Compact II General] ChrisDavis7786:
Hi

Please can someone help me, I have a charmer work phone with a specific bit of software on it, is there anyway i can extract program from it and place onto another windows mobile device. I do not have the original setup for it and really need to change phone. Any help would be much appreciated

Regards

Chris
[MDA Compact II General] dwizzy130:
It would help if you said which software....

dwizzy130
[MDA Compact II General] ChrisDavis7786:
sorry its ukaMFT if you know it?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] also1989:
hi guys,

i recently got a tp2 t7373. this is my 1st winmo phone. i was googling for apps and i came across this forum. i think that you do very good work at developing and fixing what microsoft can't.

i leave in Greece (Europe). My device has the 6.1 rom with greek language.

i want to flash a new 6.5 rom with english.

I 've search a lot about the tp2 (hspl, flashing, custum roms, etc..), but i found very little info on the device i got (t7373).

So my questions are:

- should i wait and see if htc Greece release a 6.5 rom so i don't void my warranty,yet.

- witch version of HardSPL should i install?

- can i relock my device in order not to void my warranty, in case of hardware problems in the future? if yes, how?

- is there another codename for my phone, witch i'm not aware of?

- i want to flash a stable, reliable and fast rom of 6.5 winmo. witch roms do i look for my phone?

- can i install separately the version of tf3d of my choice? does this need a new sort of flashing?

- can i flash, after i hspl my phone, roms witch are ment for other devices?

- is there any chance of bricking my phone after hspl by flashing?

- witch is the safest way to flash?

- is there anything else, in your opinion, i should know before flashing?

thanx in advance.

alex
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] greatoz:
- should i wait and see if htc Greece release a 6.5 rom so i don't void my warranty,yet.

you might wait a LONG time...

- witch version of HardSPL should i install?

the latest, if your device is supported. there are different TP2 models... look at this: http://xdaforums.com/showthread.php?t=550131

- can i relock my device in order not to void my warranty, in case of hardware problems in the future? if yes, how?

yes, provided a stock ROM is made available. refer to this: http://xdaforums.com/showthread.php?t=550131

- is there another codename for my phone, witch i'm not aware of?

depends on where and from whom you purchased it.

- i want to flash a stable, reliable and fast rom of 6.5 winmo. witch roms do i look for my phone?

there's a database thread, search and have a look. http://spreadsheets.google.com/pub?key=tBctimfdK9NM5awAG-Xnwpw&single=true&gid=0&output=html

- can i install separately the version of tf3d of my choice? does this need a new sort of flashing?

too much of a n00b to know.

- can i flash, after i hspl my phone, roms witch are ment for other devices?

sometimes, but i'd flash for YOUR device versus risking it.

- is there any chance of bricking my phone after hspl by flashing?

always. it's slight, but the answer is yes.

- witch is the safest way to flash?

there's a thread about flashing for n00bs. look at that. http://xdaforums.com/showthread.php?t=550540

- is there anything else, in your opinion, i should know before flashing?

yes, read all the threads about HardSPL, SIM unlocking (pay for it, it's worth it) and CAREFULLY review the cook's instructions before flashing the ROM of your preference.

also, use the search. http://tinyurl.com/yko3w26

tGo
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] ai6908:
If you are worried about warranty, then you shouldnt flash! And yes if you dont have stock ROM handy dont flash.
[P3300, MDA Compact III General] rui_gaia:
Hi,

can anyone help me plz? My Pda sometimes freezes and sometimes turns off and i need to take of the batery to turn on again.

Sorry but i'm noob in this stuff...

regards
[P3300, MDA Compact III General] Nele12:
Mine too

Mine too, in various moments (actions). During the phone call, typing SMS, receiving SMS etc just freezes, screen goes off (actually very dark gray) and can't do anything but to take battery out and back in and restart.

It was working fine till couple of weeks ago. Then I have tried S2U2 and some keyboard prog.

I have tried with hard reset but no luck.

Any suggestion?

Thanks in advance.

P.S. just found this:

http://xdaforums.com/showthread.php?t=543194

Seems to me that replacing the battery could be the answer!!!

good luck rui_gaia

Edit on Okt 30, 2009

Seems to me that new battery doesn't help. Same thing again. Ugh!
[P3300, MDA Compact III General] Xtremerer:
Hi

I had similar pproblems on mine and it really turned out to be the battery.
[P3300, MDA Compact III General] Nele12:
Thanks Xtremerer,

Today news:

I just got my Artemis from the service and the guy told me that I had two problems:

1. Software - he just did some kind of "repair" tool for services (not flashing)

2. Hardware - problem with mini USB connector on the bottom of the phone - he said - inspect your cables, one might be bad.

(3). Battery - I gave him the phone with the original battery although i have both the new one. He told me to change the battery, this one is bad, screen flickers because of it.

I was happy for couple of hours, but, it turned out that my WiFi doesn't work anymore :(

Any idea?
[XPERIA X1 ROM Development] dosco:
Hi all

I tried to install the Hard-SPL

but It came [error 202] to me, I am sure that the device was connected probably to the PC, and my OS is Win7.

Can any one solve this situation? I just want to update to the WM6.5:(

but seems.....I need some help from you guys...:confused:

thanks...
[G1 Android Development] farmatito:
From Wikipedia:

The NOOP scheduler is the simplest I/O scheduler for the Linux kernel.
This scheduler was developed by Jens Axboe.

The NOOP scheduler inserts all incoming I/O requests into a simple, unordered
FIFO queue and implements request merging.

The scheduler assumes I/O performance optimization will be handled at some
other layer of the I/O hierarchy; e.g., at the block device; by an intelligent
HBA such as a Serial Attached SCSI (SAS) RAID controller or by an externally
attached controller such as a storage subsystem accessed through a
switched Storage Area Network).

[B]NOOP scheduler is best used with solid state devices such as flash memory
or in general with devices that do not depend on mechanical movement to
access data (meaning typical "hard disk" drive technology consisting of seek
time primarily, plus rotational latency). [/B]Such non-mechanical devices do not
require re-ordering of multiple I/O requests, a technique that groups together
I/O requests that are physically close together on the disk, thereby reducing
average seek time and the variability of I/O service time.

To check which scheduler is used:

adb shell
~ # cat /sys/block/mmcblk0/queue/scheduler
[noop] cfq

To select a different scheduler:

adb shell
~ # echo "noop" > /sys/block/mmcblk0/queue/scheduler

To select the noop scheduler for all your block devices you can add

this lines to your userinit.sh script:

# Set "No-op" scheduler for mtdblocks and mmc
for i in `ls -1 /sys/block/mtdblock*` /sys/block/mmcblk0
do
echo "noop" > $i/queue/scheduler
done

I tested it a little and especially the sdcard seems to work faster.

Enjoy
[G1 Android Development] akirah:
Ahh, noop is set to default in my kernels, but I wouldn't say that there is BIG difference on g1.
[G1 Android Development] JD82:
Is it even better then the BFQ Scheduler used by Cyanogen?
[G1 Android Development] pentace:
Would you mind since you are willing to share this info to post some information on what settings you are finding work best and such?

To post this type of info without it being watered down a bit for ever level of user can and probably will cause issues from people going into settings only half knowing what they are doing. Granted if you don't know what you are doing you shouldn't be, but we all know its going to happen
[G1 Android Development] farmatito:
I tested it on a Cyanogen Mod 4.0.4 with self compiled kernel 2.6.29.6

from cyanogen's git repository. The available schedulers are noop and cfq.

The default scheduler was cfq and after having read about noop scheduler

i tried it and found no regression in performance but rather some improvement.

I have no benchmarks yet. So you have to test it yourself

to see if it makes a difference on your phone. I cannot imagine

this mod causing issues as it is easily reverted and it was not intended

for all users but rather for the tech savvy to see if they can confirm

some improvement in performance.
[G1 Android Development] akirah:
It's I/O scheduler.
[G1 Android Development] JD82:
I've made a typo: it is BFQ, not BFC.

From the cyanogenmod's changelog:

From my G1:

adb shell
# cat /sys/block/mmcblk0/queue/scheduler
noop [bfq]

Again: Is it even better then the BFQ Scheduler used by Cyanogen?
[G1 Android Development] shafty023:
Excellent tip, thanks!
[G1 Android Development] Afirejar:
Yeah well, anticipatory is back now in the new stable build.

cat /sys/block/mmcblk0/queue/scheduler
noop [anticipatory]
[G1 Android Development] farmatito:
I tested it only vs cfq scheduler, so I can't say if it is better than anticipatory

or cfq scheduler. The rationale behind this change is that flash and mmc don't need a scheduler so there should be a performance gain for the reason that

that we use simpler/less kernel code with littler data structures in memory.

Time and user reports will tell it the change is worth the effort.
[G1 Android Development] cyanogen:
I've tried them all and keep going back to the anticipatory iosched. Everything just seems smoother. Maybe the devices like the io reordering that it does.
[G1 Android Development] JD82:
Thanks, this is the best answer I could hope :D
[G1 Android Development] farmatito:
From Wikipedia, the free encyclopedia

Anticipatory scheduling is an algorithm for scheduling hard disk input/output.
It seeks to increase the efficiency of disk utilization by "anticipating"
synchronous read operations.

"Deceptive idleness" is a situation where a process appears to be finished
reading from the disk when it is actually processing data in preparation of the
next read operation. This will cause a normal work-conserving I/O scheduler
to switch to servicing I/O from an unrelated process. This situation is
detrimental to the throughput of synchronous reads, as it degenerates into a
seeking workload. Anticipatory scheduling overcomes deceptive idleness by
pausing for a short time (a few milliseconds) after a read operation in
anticipation of another close-by read requests.

Anticipatory scheduling yields significant improvements in disk utilization for
some workloads. In some situations the Apache web server may achieve up
to 71% more throughput from using anticipatory scheduling.

The Linux anticipatory scheduler may reduce performance on disks using
TCQ, high performance disks, and hardware RAID arrays. An anticipatory
scheduler (AS) was the default Linux kernel scheduler between 2.6.0 and
2.6.18, by which time it was replaced by the CFQ scheduler.

Judging by this description "as" scheduler should be doing no good to mmc or

flash as there are no moving parts as in hard disk. I think we should do some

benchmarking. Ideas?
[G1 Android Development] farmatito:
Some rough benchmarks:

A) Wrinting a 10MB file to sdcard:

1) with anticipatory scheduler

time dd if=/dev/zero of=/sdcard/test.bin bs=1M count=10
10+0 records in
10+0 records out
real 0m 2.63s
user 0m 0.22s
sys 0m 0.30s

2) with noop scheduler:

time dd if=/dev/zero of=/sdcard/test.bin bs=1M count=10
10+0 records in
10+0 records out
real 0m 0.64s
user 0m 0.10s
sys 0m 0.33s

B) Reading 10MB file from sdcard:

1) with anticipatory scheduler:

time cat /sdcard/test.bin
real 0m 6.32s
user 0m 0.93s
sys 0m 0.02s

2) with noop scheduler:

time cat /sdcard/test.bin
real 0m 6.35s
user 0m 0.93s
sys 0m 0.01s

C) Writing a 10 MB file to flash:

1) with anticipatory scheduler:

time dd if=/dev/zero of=/data/test.bin bs=1M
10+0 records in
10+0 records out
real 0m 4.04s
user 0m 0.81s
sys 0m 0.04s

2) with noop scheduler:

time dd if=/dev/zero of=/data/test.bin bs=1M count=10
10+0 records in
10+0 records out
real 0m 4.09s
user 0m 0.81s
sys 0m 0.05s

D) reading a 10MB file from flash:

1) with anticipatory scheduler:

time cat /data/test.bin
real 0m 6.33s
user 0m 0.90s
sys 0m 0.01s

2) with noop scheduler:

time cat /data/test.bin
real 0m 6.32s
user 0m 0.88s
sys 0m 0.01s

On the sdcard anticipatory and noop scheduler have similar performance when reading, but noop is a lot faster when writing.

On flash memory they have similar performance in reading and writing.

I prefer noop as the code is simpler with less overhead for the system.

Any ideas about better benchmarking are welcome.
[G1 Android Development] dumfuq:
Just wondering if this was a single run test or multiple using averages?
[G1 Android Development] JD82:
+1

In Android, where do I place the command to be executed automatically? Is there a rc.local or equivalent?
[G1 Android Development] farmatito:
The test results are indicative values of a few test runs.

To automate the setup commands could be added to userinit.sh
[G1 Android Development] JD82:
I've made a very simple script to iterate 10 times with the noop and anticipatory scheduler.

#!/system/bin/sh

IOSCHEDULER="anticipatory"

writesd()
{
cat /sys/block/mmcblk0/queue/scheduler
for i in `seq 1 10`;
do
time dd if=/dev/zero of=/sdcard/test.bin bs=1M count=10
done
rm /sdcard/test.bin
}

cat /sys/block/mmcblk0/queue/scheduler | grep -q $IOSCHEDULER
if [[ $? -ne 0 ]]
then
echo "Please set the correct scheduler by editing the script"
exit 1
fi

echo "noop" > /sys/block/mmcblk0/queue/scheduler
writesd

sleep 2
echo $IOSCHEDULER > /sys/block/mmcblk0/queue/scheduler
writesd

The output on my G1:

[noop] anticipatory
10+0 records in
10+0 records out
real 0m 2.71s
user 0m 0.00s
sys 0m 0.52s
10+0 records in
10+0 records out
real 0m 1.43s
user 0m 0.01s
sys 0m 0.49s
10+0 records in
10+0 records out
real 0m 1.74s
user 0m 0.00s
sys 0m 0.47s
10+0 records in
10+0 records out
real 0m 1.55s
user 0m 0.01s
sys 0m 0.48s
10+0 records in
10+0 records out
real 0m 1.21s
user 0m 0.00s
sys 0m 0.57s
10+0 records in
10+0 records out
real 0m 1.09s
user 0m 0.00s
sys 0m 0.43s
10+0 records in
10+0 records out
real 0m 1.95s
user 0m 0.00s
sys 0m 0.43s
10+0 records in
10+0 records out
real 0m 1.89s
user 0m 0.00s
sys 0m 0.45s
10+0 records in
10+0 records out
real 0m 1.53s
user 0m 0.00s
sys 0m 0.43s
10+0 records in
10+0 records out
real 0m 1.21s
user 0m 0.00s
sys 0m 0.54s

noop [anticipatory]
10+0 records in
10+0 records out
real 0m 1.38s
user 0m 0.00s
sys 0m 0.46s
10+0 records in
10+0 records out
real 0m 1.22s
user 0m 0.00s
sys 0m 0.45s
10+0 records in
10+0 records out
real 0m 1.94s
user 0m 0.00s
sys 0m 0.48s
10+0 records in
10+0 records out
real 0m 1.60s
user 0m 0.00s
sys 0m 0.48s
10+0 records in
10+0 records out
real 0m 1.82s
user 0m 0.00s
sys 0m 0.47s
10+0 records in
10+0 records out
real 0m 1.21s
user 0m 0.00s
sys 0m 0.59s
10+0 records in
10+0 records out
real 0m 1.42s
user 0m 0.00s
sys 0m 0.56s
10+0 records in
10+0 records out
real 0m 1.88s
user 0m 0.00s
sys 0m 0.42s
10+0 records in
10+0 records out
real 0m 2.05s
user 0m 0.00s
sys 0m 0.49s
10+0 records in
10+0 records out
real 0m 1.50s
user 0m 0.00s
sys 0m 0.48s

I don't see any big difference. The values fluctuate a lot.
[G1 Android Development] cyanogen:
You also have to consider the many readers/writers situation. I think the AS should be better here (CFQ even more so, but CFQ has more overhead).
[G1 Android Development] JD82:
Of course, I just wanted to check if the noop is realy always better for the SD, as could perhaps infer from the post of farmatito :)

PS

Your ROM is amazing! Thanks! :D
[G1 Android Development] farmatito:
Some more benchmarks. I've written two little C programs (mostly taken from

busybox's hdparm) and a script to loop through all schedulers.

Benchmarking works in reading and writing mode for mmc

and in reading mode only for mtd. Sources, binaries and script are

attached. I can confirm that there seems not to be a big difference

between the different schedulers with better bechmarking tools.

sched_test.sh
Testing: read dev/block/mmcblk0
noop 46 MB in 3.05 seconds = 15394 kB/s
anticipatory 45 MB in 3.01 seconds = 15286 kB/s
deadline 44 MB in 3.00 seconds = 14969 kB/s
cfq 40 MB in 3.01 seconds = 13601 kB/s
bfq 43 MB in 3.00 seconds = 14632 kB/s
Testing: write dev/block/mmcblk0
noop 90 MB in 3.00 seconds = 30716 kB/s
anticipatory 100 MB in 3.20 seconds = 31976 kB/s
deadline 90 MB in 3.05 seconds = 30195 kB/s
cfq 100 MB in 3.27 seconds = 31234 kB/s
bfq 100 MB in 3.20 seconds = 31985 kB/s
Testing: write dev/block/mtdblock5
noop 10 MB in 3.92 seconds = 2605 kB/s
anticipatory 10 MB in 3.76 seconds = 2720 kB/s
deadline 10 MB in 3.77 seconds = 2715 kB/s
cfq 10 MB in 3.75 seconds = 2726 kB/s
bfq 10 MB in 3.77 seconds = 2713 kB/s
/system/sd/bin # sched_test.sh
Testing: read dev/block/mmcblk0
noop 44 MB in 3.03 seconds = 14848 kB/s
anticipatory 46 MB in 3.04 seconds = 15445 kB/s
deadline 49 MB in 3.04 seconds = 16476 kB/s
cfq 45 MB in 3.05 seconds = 15081 kB/s
bfq 44 MB in 3.04 seconds = 14787 kB/s
Testing: write dev/block/mmcblk0
noop 100 MB in 3.20 seconds = 31954 kB/s
anticipatory 100 MB in 3.23 seconds = 31677 kB/s
deadline 100 MB in 3.20 seconds = 31955 kB/s
cfq 100 MB in 3.26 seconds = 31380 kB/s
bfq 100 MB in 3.18 seconds = 32124 kB/s
Testing: write dev/block/mtdblock5
noop 10 MB in 3.93 seconds = 2601 kB/s
anticipatory 10 MB in 3.76 seconds = 2722 kB/s
deadline 10 MB in 3.77 seconds = 2709 kB/s
cfq 10 MB in 3.81 seconds = 2684 kB/s
bfq 10 MB in 3.83 seconds = 2667 kB/s

Would have been nice to see some benchmarks also for reading mtd but i

was not able to make the read_test program work with flash memory yet.
[G1 Android Development] wesgarner:
Hey CM, pulling the /proc/config.gz from your latest ROMs shows that you are back to using CFQ...?
[G1 Android Development] alapapa:
Not the case for me:

bash-3.2# zcat /proc/config.gz | grep -i cfq
# CONFIG_IOSCHED_CFQ is not set
# CONFIG_DEFAULT_CFQ is not set

also

bash-3.2# cat /sys/block/mmcblk0/queue/scheduler
noop [anticipatory]
[G1 Android Development] Lollipop_Lawlipop:
hmmm that's not the case for me... terminal reads CFQ
[G1 Android Development] ivanmmj:
I'm also getting:

cat /sys/block/mmcblk0/queue/scheduler
noop [anticipatory]
[G1 Android Development] lordofazeroth:
Hello.

I did this on my Archos with Android 2.2, it was working perfectely.

Now I have a new tablet with Android 3.0.1, Gtabcomb.

When I enter

it says, no such file or directory.

Is this working on HC too?
[G1 Android Development] tearsphere:
I wanna try this on my mytouch running senselx 4.2 .... just don't know exactly what to do.... pls help
[G1 Android Development] hrk:
Install my No-frills CPU Control app and choose the I/O scheduler (4th option).
[G1 Android Development] gu5t3r:
Your code does not work on Arc S ICS, "ls -1" gives error.

I modified your code to work:

# SET "No-op" scheduler for mtdblocks and mmc

for i in `ls /sys/block/mtdblock*` /sys/block/mmcblk0; do
echo "noop" > "$i/queue/scheduler";
done

and made script 69Noop4All for init.d which is in attachment...

Also made script test_scheduler.sh for Script Manager to check schedulers.

It gives output like this:
[G1 Android Development] Neo2SHYAlien:
I prefer deadline. Deadline is a bit faster. But if are using swap CFQ is best choice
[G1 Android Development] farmatito:
I think ROW scheduler http://lwn.net/Articles/509829/ might even be faster.....

Enjoy.
[G1 Android Development] gu5t3r:
But noop should save battery....
[G1 Android Development] Neo2SHYAlien:
which scheduler is faster is not so important. Because fast phone with short battery life is nothing ;)

Yeap but battery usage differences between noop and deadline is not so much :) CFQ drain more battery but when system start defragmentation over swap partition CFQ is better.
[G1 Android Development] :
looks promising..
[G1 Android Development] ryree0:
I'll report back after some testing; nothing extremely interesting so far, though.
[G1 Android Development] roalex:
noop was ok years ago, BFQ is 5% faster, which is not a lot though. At least on my tests.
[Touch Pro2, Tilt 2 Windows Mobile General] orb3000:
Hi all

My problem is every time I connect my TP2 to my lap top it starts WMDC perfectly but no sync at all.

Then I go to my device and ask from there to start sync, so it starts but it never finishes....

So no sync after all my attempts

I have Energy´s latest photon ROM without any other extra app installed.

I´ve tryed to untick the "enable faster data transer" in usb to pc

Any help is much apreciated:)

Thanks,
[Touch Pro2, Tilt 2 Windows Mobile General] orb3000:
Bump:)

Any ideas?
[Touch Pro2, Tilt 2 Windows Mobile General] DaveTheTytnIIGuy:
I'm using EnergyROM build 21864 and have the same problem. What you need to do is go to USB to PC settings, tap the radio button next to "ActiveSync (Sync with Outlook)", and untick the box at the bottom that says "Ask me first about USB connection type when I connect the device to the PC". Unplug your device from the PC, plug it back in, and see if it works. It worked perfectly for me.
[Touch Pro2, Tilt 2 Windows Mobile General] orb3000:
Thanks Dave

It worked!

Cheers,
[Touch Diamond2, Pure Themes and Apps] left of centre:
Hi Dev's.

Any chance of anyone putting together a National Rail Enquiries Client like the Iphone one found here

Would be very useful I'm sure. The WAP version isn't bad but a client would be quicker and easier.

Thanks.
[Touch Diamond2, Pure Themes and Apps] bilal671:
Yeah this would be majorly useful for me too :). I did look around for one but never found one that was any good :(.
[Touch Diamond2, Pure Themes and Apps] MartyH32:
I know u mentioned the Wap site have you tried the PDA version MUCH better its

pda.ojp.nationalrail.co.uk

Its the one that I always use, the WAP is a bit more basic.

APP would be great :)
[Touch Diamond2, Pure Themes and Apps] jonathanfoster:
would a great app and very usefull if some one could port this to WM :)
[Touch Diamond2, Pure Themes and Apps] Superman_1122:
I'm hoping with the inclusion of Marketplace on WM6.5 lots of apps will appear that were popular on Iphones :)
[Touch Diamond2, Pure Themes and Apps] jonathanfoster:
yes i am hoping we are going to see more but alot at the moment are not free and there doesnt seem to be many that are free..

and some are really expensive i think..
[Touch Diamond2, Pure Themes and Apps] left of centre:
Thanks for the suggestion Marty. You're right, the PDA version is better than the WAP version.
[Touch Pro2, Tilt 2 Windows Mobile General] ucanthang29:
I got my Touch pro 2 from att about a little over a week ago. Now I must have flashed 10 roms on the phone so far. I used to have the first generation tilt for 2 years. Going from that to the new tilt 2 I am not that impressed with the difference in speed. I am wondering was the first generation tilt fully pimped out really that good for what it was or do we still have a way to go with the tp2 as far as development goes. That aside I feel the speed is only marginally better so far, aside from the hardware differences I am wondering, is this as good as it is going to get? Any other opinions about this? Just wondering what the consensus is.