yashsingh1/xdaforums huggingface dataset:
[Touch Cruise General] murwin:
I also have strange problems. My Cruise dropped on the floor on a skiing trip last March, and since than it has strange network problems.

It mostly says 'No service', but sometimes (randamly) it says something like 'Searching...', 'Denied,Searching...'

I'm not sure if I translated this correctly, I have a Dutch version of the standard 6.1 ROM. I hard reset, re-flashed to original firmware RUU_Polaris_HTC_NLD_3.13.404.0_radio_sign_25.85.30.07_1.59.42.15_Ship.exe

Since this afternoon it is not connecting at all. No reception at all.

My provider is the Dutch one Vodafone (it shoud say '3G Vodafone NL'). Funny is that the those items are unchecked in the network selection (phone --> network --> select networks), but that seems to be the case with other users as well.

Does anyone has a clue?

Greetings,

Murwin.
[Touch Cruise General] missioncontrol:
Same Problem

My Polaris randomly goes offline and gives the ! mark next to the signal meter. I have tried changing Radio ROM and it makes not difference. I think the problem is with the SIM Card reader. I put some sponge tape over the top of the SIM Card reader so it puts even downward pressure on it and the problem is almost fixed. It still randomly goes offline, but only once a day now. If anyone has had any better luck, please post the solution here.

Thanks
[Touch HD Windows Mobile ROM Development] danprocter:
I'm thinking of flashing to Dutty's rom, but have no idea on where to start. I have read through all sorts but its still all confusing to me. A step by step instruction/guide would be of great help.

Thanks
[Touch HD Windows Mobile ROM Development] Snuurtje:
Dude, try the wiki, everyone has to do this.

Start here: http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Flash1
[Touch HD Windows Mobile ROM Development] Sir.B:
easy 4 step proccess

1. drop Touch HD into a padded envelope

2. mail it to me

3. ???

4. profit
[Touch HD Windows Mobile ROM Development] funk1980:
Use the search Luke!
[Touch HD Windows Mobile ROM Development] deepakjohn:
You don't mean!:p:rolleyes:
[Touch HD Windows Mobile ROM Development] kaiser_chef:
lmao you could make a lot of money in noob rom flashing
[Touch HD Windows Mobile ROM Development] Caid444:
Hey Dan.

Someone here linked the wiki for the Touch HD. I know it's a bit overwhelming when you first entertain the prospect of flashing a new rom on your phone. You want someone to lead you through it step by step, you don't want to brick your phone, and you want to know which ROM is best.

I don't know which ROM is best, everyone has their favourite.

Start with Davidduek's V3-HP, or Dutty's 2.3 extreme.

They're both very good roms, the latest software, and you'll notice a big difference from the phone you have now.

As for how to do it. Overwhelming at first? YES. Impossible? NO.

Take things step by step. There is a complete step by step guide on the wiki.

Your fear of doing something wrong and killing your phone, it's something we all had at the start. I will say this, if you follow the steps (and remember to breath every now and again) you'll have your first flashed rom on your phone in no time. Not to mention, the high of actually getting it done (it really is gratifying)

So, go to the wiki, look for the guide. Follow it.

Good luck my friend, and don't worry, get it done.

Caid.
[Touch HD Windows Mobile ROM Development] stefh:
I had the same in the beginning as most tutorials somehow sound very risky, but in reality it is really easy.

I never backup my contacts, calendar or whatever, so that's up to you if you want to do that first.

I use USPL instead of HSPL as it should be safer for your warranty. I can go into technical details, but in my opinion that is not that important.

See it this way, normally you are not able to flash roms that are not officialy from HTC and USPL makes this possible. Simple as that.

I tried to make the tutorial as easy as possible:

STEPS

1. download USPL onto your PC (of course you need your PC for flashing) and download the rom you want to put on your phone and have them ready.

(Most rom zips contain the rom and an excecute file to start the flashing process, if it does only contain the rom, you have to download this excecute file seperately, it is called custom RUU, or you can take it out of a rom zip which contains it)

2. Go to ActiveSync properties in your PC's taskbar and disable "Allow USB Connections" option. (right click on the icon and you will see that option)

3. Turn off your phone

4. Switch your phone on in "Flashing mode" (you will see a tri-color screen) by pressing and holding "Power" and "VolDown" keys simultaneously.

5. Wait a couple of seconds

6. Connect a USB cable from PC into your phone and make sure the text "USB" appears on your phone's screen (in the white portion of the screen)

7. Start USPL by clicking on blac_uspl.exe on your PC.

8. On your phone, USPL text and some numbers appear.

9. Now you can run the exe file (custom RUU) from your PC and be sure the rom is in the same folder as this exe file.

10. Just follow the on screen instructions on your PC.

11. The flashing progress is shown on your PC and on your phone. When it is at 100%, wait until you get the message everything is ok on your PC. From that moment you can disconnect your phone and switch it on again and enjoy your new ROM! :D

It is recommended to do a HARD RESET on your phone after flashing to get optimum perfomance and stability inside your new ROM. See your manual how you can HARD RESET.
[Touch HD Windows Mobile ROM Development] Gustopher:
With the very greatest of respect to you stefh, the community would be far better served by your adding this excellent guide to the Wiki rather than addressing a specific post - otherwise this gets buried in the noise.

I tend to agree with earlier posters that we all had to sit down and invest time in understanding the process - resources such as the Wiki have been created for just such a reason.

Fundamentally if you have read the Wiki and still don't understand the process (or don't feel able to follow the steps) flashing ROMs is probably not where you need to be at this point in time.

I'd certainly see about getting this added to the Wiki though...
[Touch HD Windows Mobile ROM Development] stefh:
Thanks iain for pointing that out. I will put in on the wiki when I get home if it is appreciated.

I agree one should not Flash if one does not know what he is doing.

But when I look back on my personal situation.

I always used Symbian and in fact the Touch HD is my first winmo phone.

I have experience with doing all kinds of firmware flashes and "hacking" with a variety of equipment (Symbian phones, Sony Ericsson "standard" phones, PC equipment, popcorn hour, etc.)

And somehow I found it difficult to simply understand all the steps needed for a device like the blackstone. But when I just did it, it was so easy I was like: "Man! Why did I had any doubts?"

Same thing goes for that I do not understand why everybody always uses the codenames(concept names) for the phones like blackstone, topaz and rhodium as for someone new it is not as easy to immediately understand what it is all about. I guess there never was any bad intention on purpose, but I read a lot of stuff of which I think: damn why make it so difficult when it is so easy? It is like it is a sport or something to mask the simple terms ;)

e.g. When we just talk about touch HD, touch pro 2, diamond 2 it gets much easier. I can understand it is done to keep people with less knowledge in this scene away, but not all new people to the scene are noobs.

Of course it is not my intention to insult people. I have really deep respects for all active people working their ass of creating (sorry cooking) new roms and stuff.

When I was a student I had all this free time to go deep and look everything up, but when you work, you do not have all this free time anymore but you still want to integrate in the forum and sometimes it is really nice if someone simplifies things for you. But of course I know a rush is never good. It is important to think everything through and of course to learn.

But is also important to give your girlfriend enough attention ;)

I want to thank everyone on this forum that made my Touch HD what it is now :) Respect
[Touch HD Windows Mobile ROM Development] skribzy:
well said sir! :)
[G1 Themes and Wallpapers] dmm0816:
Is there a way to add/change wallpapers to the wallpaper gallery when you press menu and wallpaper from the home screen? sorry if this is a dumb question ive been tryin to figure it out and can't...thanks.
[G1 Themes and Wallpapers] punkweakling:
Pretty sure they're system files man.

Use the app Wallpaper Set and Save to set full quality wallpapers from your SD card (with none of that crappy jpg compression).
[G1 Themes and Wallpapers] dmm0816:
oh ok....thanks man.
[G1 Themes and Wallpapers] Boeboe:
when I put wallpapers on my SD card in bmp or png format I don't see any compression artifacts at all with the default "set as wallpaper" feature, as opposed to jpg files.
[Upgrading, Modifying and Unlocking] Neilyboy:
I have an xv6800 that a buddy of mine gave me after an upgrade. It is currently running a sprint rom v3.35.651.2 (02/22/08). Radio Version 3.35.04. I am not wanting to service the phone in any way but just use it as a 'portable pc, to check email with when wi-fi networks are available' as well as a 'gps unit'.

I have done the hardspl (unlock)

I have updated the radio (3.35.04)

then threw on this sprint rom (3.35.651.2)

(configured the proper port settings)

I for the life of me can not get the gps unit to work. I know the phone (before I had it) was unlocked and running the gps. The same guy who owned the phone before me has also tried to unlock it from scratch again and get it back 'online' with no success.

I am wondering if an active voice plan on it is needed to enable the gps? I have tried to run through the tutorials myself a handful of times and still not able to get this thing to work with gps. Any help or information is much appreciated!

Neil
[Touch Pro, Fuze General] thehyecircus:
I've had my Fuze since launch but I am too scared to do anything other than install .cab's, and I'm thinking it's time to change that. Can anyone help me? You can PM me if you want, before this gets deleted.
[Touch Pro, Fuze General] thehyecircus:
Bumping for more visability.
[Touch Pro, Fuze General] kareeem:
I can help you on AIM. My information is in my profile.

Thread closed.
[G1 Android Development] SilentMobius:
Hi all,

I've been pondering the whole "apps on sdcard" thing since I got my 16Gb microsdhc card (class 2, so 2MB/s, the slowest), I've even made a 4GB ext2 partition ready for it.

So I've finally got around to looking at the data partition to see what I can do.

Now firstly plenty of people refer to the phones "memory" which isn't very useful really, since we don't have any fixed disks it is all "memory" at the hardware level but "system memory" is different to the memory that is only ever used as storage.

So, The /data partition is on the NAND flash that the G1 has even without an sdcard installed, the larger directories seem to be:

/data/data #App data, 28MB on my system
/data/app # non system apps, 12MB on my system
/data/app-private # protected apps, 266kB on my system
/data/dalvik-cache # The compiled .dex files for _all_ installed apps, 10MB on my system

So, apps are found in either /system/app /data/app or /data/app-private I wonder if there's anywhere else that android looks by default?

I also can't help but wonder if I should move the davlik-cache folder. Common wisdom is that it would be much slower, especially on a class2 microsdhc so I decided to run a little test

dd if=/dev/urandom of=tst0.bin bs=1M count=1
date
cp tst0.bin tst1.bin
rm tst0.bin
cp tst1.bin tst2.bin
rm tst1.bin
cp tst2.bin tst3.bin
rm tst2.bin
cp tst3.bin tst4.bin
rm tst3.bin
cp tst4.bin tst5.bin
rm tst4.bin
cp tst5.bin tst6.bin
rm tst5.bin
cp tst6.bin tst7.bin
rm tst6.bin
cp tst7.bin tst8.bin
rm tst7.bin
cp tst8.bin tst9.bin
rm tst8.bin
date

Executing this in /sdcard/ had it complete in about a second which seems to be faster that should be possible so there may well be aggressive write and read caching going on there. Having said that 2MB/s is the minimum speed for the card.

However, doing the same in /data/ took 21 seconds, that's about 0.5MB/sec so I'm wondering if there really are any speed problems running as much as possible from the sdcard.
[G1 Android Development] Autarkis:
I suspect your suspicion of aggressive SD caching is correct.

If that were the case, you have measured only the speed of the cache. ;)

A small scenario: Let's say your phone shuts down, all apps are terminated and write final stuff in /data/. Then, the writing process is being cached (the parameter in /etc/fstab is "nosync" I think). But before the cache is being written (by pdflush), the power would go away! Then the data would be lost, possibly requiring a reinstall of the app.

As to your command, I think it's a mistake to define the blocksize as 1 MB and the count as 1. That way, 1 MB is first being cached by dd into one block which is then written. (That just occured to me.)

I just did:

$ su
# time dd if=/dev/urandom of=/sdcard/random.bin bs=1 count=1024000

and the output was:

1024000+0 records in
1024000+0 records out
real 0m 49.50s
user 0m 3.46s
sys 0m 44.70s

What's yours? :D

Edit: I forget the important thing:

$ su
# time dd if=/dev/urandom of=/data/random.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real 0m 54.90s
user 0m 4.71s
sys 0m 45.13s

It seems to be about the same speed on my device.
[G1 Android Development] LucidREM:
your partition is too large for EXT2 and will not work properly .. you need to size it 2G or less .. you really shouldn't need anything above 500M
[G1 Android Development] SilentMobius:
Really? I was under the impression that ext2 could go a lot larger than that, there were 2GB file size limits under 2.2 kernels and older libc's but I wasn't aware of any filesystem size limits that small.

Thinking about the tests, the reason I started monitoring after the copy from urandom was that that operation was pretty slow regardless where it was run (urandom generally blocks until it gets enough entropy etc etc) so I didn't include it in my calculations.

Perhaps sticking in periodic "sync"s will help.... or I guess I could remount the sdcard as synchronous and hope that mountd doesn't get arsey

I'll have another look tonight
[G1 Android Development] Nitro212:
i got this is it good?

sdcard results

# time dd if=/dev/urandom of=/data/random.bin bs=1 count=1024000
time dd if=/dev/urandom of=/data/random.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real 0m 47.49s
user 0m 3.52s
sys 0m 42.91s

/data/ results

# time dd if=/dev/urandom of=/data/random.bin bs=1 count=1024000
time dd if=/dev/urandom of=/data/random.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real 0m 46.87s
user 0m 4.08s
sys 0m 41.36s
[G1 Android Development] unrafa:
/dev/urandom is a bad way of measuring sd card speed since urandom makes intensive use of cpu and results will vary depending on processor speed / processor load etc.

in case, use dd if=/dev/zero which is less processor ungry
[G1 Android Development] Nitro212:
big difference i just ran it on the sdcard can got this

# time dd if=/dev/zero of=/data/random.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real 0m 19.75s
user 0m 3.11s
sys 0m 15.82s
[G1 Android Development] Autarkis:
Thanks for that information! :eek: I was under the misconception that the ARM CPU could put out numbers faster than could be written to SD. :p

Rerunning the test now...

# time dd if=/dev/zero of=/data/random.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real	0m 23.62s
user	0m 3.47s
sys	0m 15.78s
# time dd if=/dev/zero of=/sdcard/random.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real	0m 21.80s
user	0m 3.59s
sys	0m 17.89s
#

So, even on my Class 2 card, writing /data is about as fast as writing /sdcard. That's good news for further experimenation. :)

I also tried reading from the device in blocks of one byte and writing; turns out reading takes about a third of the time. Again, internal and external (SD) NAND are the same speed at class 2.

# time dd if=/data/random.bin of=/data/random2.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real	0m 33.15s
user	0m 2.65s
sys	0m 24.47s
# time dd if=/sdcard/random.bin of=/sdcard/random2.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real	0m 34.38s
user	0m 2.99s
sys	0m 29.03s
#
[G1 Android Development] Nitro212:
this is from a class 2?

# time dd if=/dev/zero of=/data/random.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real	0m 23.62s
user	0m 3.47s
sys	0m 15.78s
# time dd if=/dev/zero of=/sdcard/random.bin bs=1 count=1024000
1024000+0 records in
1024000+0 records out
real	0m 21.80s
user	0m 3.59s
sys	0m 17.89s
#

not much difference from my class 6 A-Data :/
[G1 Android Development] Autarkis:
Yea, these are my results. I use a SanDisk 16GB Class 2. Would you post your exact results as well? I'm interested in what "not much difference" means. Maybe your card is faster at reading?
[Touch HD General] nikki-m:
I appreciate that this might be similar to other threads, but none seem to be giving me any clues or answers, hence the need for a new one.

My wifi connects to my home network, and the pda reports back as connected. However, I can't get any programs to connect through it any more.

I don't use a GPRS data connection. My USB connection works fine when connected to my desktop. However, when relying only on the wifi connection, I get no joy. I had it working just fine until a few days ago - not changed or added anything, apart from re-installing s2u2 (and subsequent uninstalling it has made no difference).

Can anyone shed any light on why the wifi no longer wants to play, and any suggestions on a cure for this? Please?

Nikki
[Tilt, TyTN II, MDA Vario III General] Empire101:
I recently falshed the new WM6.1 ROM from the HTC website. The only problem I can't seem to get around is when the phone is locked and put in sleep mode, a few seconds later the screen will flash white for a second. And then periodically blink white. Mainly I don't want to waist precious battery life. Its now driving me insane. I've looked and searched for hours on hours and can't find anything like this.:confused:

I've hard reset, soft rest. Got rid of the bloatware. But still got this blink.

Any help would be greatly appreciated!

Thanks in advance!
[Tilt, TyTN II, MDA Vario III General] redbandana:
I've came across this several times with many 6.1 roms. I am not sure if a fix exists. However, this has never bothered me. I simply click the power button twice and the blinking stops. Hope this does the same for you.

All The Best.
[Tilt, TyTN II, MDA Vario III General] jonathanrobertbolton:
Same thing happens to me. I will be watching to see what the response is. Bugs me too. No idea how many times that's happening while it's in my pocket or something - not good for battery life and can't be good for the screen either...
[Tilt, TyTN II, MDA Vario III General] Flying Kiwi:
As already mentioned several WM 6.1 ROMs suffers from screen flashes relating to power management issues. Using the latest HTC WWE WM 6.1 ROM the TyTN II will occasionally require two button presses to come out of power saving mode.

If you were happy/happier with the WM 6.0 ROM complain to your ROM provider and if necessary request it be reverted (or read up here and once you know whats required, do it yourself). I don't see any 'new' official ROMs coming for this device now it's comparitively elderly, so I think it'll be up to you to come up with a solution.
[Tilt, TyTN II, MDA Vario III General] thaker_bhavesh:
HTC has provided an HotFix for that issue at :

AT&T Tilt WM 6.1 Backlight HotFix

But Truely speaking, I installed and it didn't worked for me.

It might work for you, so just give a try.

Regards,
[Tilt, TyTN II, MDA Vario III General] Empire101:
Thanks guys. I'll try the double push of the power button and see if it works, if not I live with it a little longer, till I go mad.:eek:

If I can't take it anymore I'll just re-flash to a different ROM.

Once again, thanks for the replies.

By the way the BACKLIGHT HotFix didn't work for me either. I think thats mainly to fix issues with the backlight timer always reverting back to 10 seconds, no matter what the user setting is.
[Touch HD General] farzadus:
the WM 6.5 beta version is out

can it be flashed on the HD ????

if so is flashing back to 6.1 possible???
[Touch HD General] afr33s:
Take a look at the forum

Check the ROM forum.

YES!
[Tilt, TyTN II, MDA Vario III General] jonathanrobertbolton:
AT&T Full strength "3G" connection is only clocking in at around 350kbps. Horrible. Edge is more like 120kbps.

I am using Medianet, have the PDA connect plan (that they forced me into), and even went to the trouble to utilize the "restore proxy" program in "tools" - no matter - still 350kbps. Sometimes it will come in over 400, but not often.

Wouldn't be so frustrating if it weren't for the fact that I'm sitting there with my wifes 3G iphone on the same network in the same place using the same speed test and she will regularly come in around 1400kbps.

Called AT&T to no avail. They said they were going to research it and set up an appointment to call me back even, but then they no-showed the appointment and never called.

What on earth am I doing wrong? How can I speed this thing up?
[Tilt, TyTN II, MDA Vario III General] azazelx:
Have you tried changing ur connection settings to AT&T ISP instead of medianet? That always gets me super fast speeds.
[Tilt, TyTN II, MDA Vario III General] jonathanrobertbolton:
Haven't tried that - was under the impression that you had to have the "tethering" plan to utilize the ISP address.

Is that my problem? Anyone else having medianet speed issues? What speeds are others getting?
[Tilt, TyTN II, MDA Vario III General] redbandana:
what site are you using and maybe we can compare?
[Tilt, TyTN II, MDA Vario III General] himalayasplaya:
Try enabling HSDPA and see the difference
[Tilt, TyTN II, MDA Vario III General] khaytsus:
And if you're doing it ON the phone, you're doing it wrong. USB tethered I see about 2000k/sec here sometimes, but more typically 1400. On the phone itself I MIGHT see 700k.
[Tilt, TyTN II, MDA Vario III General] jonathanrobertbolton:
Tried enabling hsdpa - but no difference. Suposedly its already enabled on these phones - just reads "3g" all the time.

Also trying tethered and getting the exact same speeds.

Using dslreports.com - they have a lowbandwidth that works well with phones...

Other thoughts?
[Tilt, TyTN II, MDA Vario III General] One Hype:
Thanks. I just tried this, but for some reason it can't connect, and no proxy is not enabled. Any ideas?
[Tilt, TyTN II, MDA Vario III General] RuizGT:
Same here.
[Tilt, TyTN II, MDA Vario III General] megatec45:
Are you able to do this without a tethering plan? I've tried to enable and it doesn't work. I do have the PDA unlimited plan. Any special settings needed other than changing from Media Net to AT&T ISP in the Network Management settings?
[Tilt, TyTN II, MDA Vario III General] boss1234:
try mobilespeedtest.com. I get between 4mb and 6mb down, consistently. Until a month ago I never got higher than 400 to 700k. It does seem loads snappier. Come to think of it, I did upgrade to wm6.1 about the same time, and I do have HSDPA enabled via kaiser tweaks.

ATT TILT

Stock WM 6.1 minus the bloatware
[Tilt, TyTN II, MDA Vario III General] gthing:
I don't know what you're doing exactly, but what you need to do is change your access point from wap.cingular to isp.cingular.

Last I checked, any plan over $30 gave you access to isp.cingular, but that may have changed. You can always use it, but if your plan doesn't have it they might charge you per kb. If that happens, I've never heard of a case where AT&T wouldn't remove the resulting charge.
[Tilt, TyTN II, MDA Vario III General] gthing:
AT&T has been rolling out support for 7.2Mbps HSDPA, you probably just got it in your city. Where do you live?