yashsingh1/xdaforums huggingface dataset:
[Touch HD General] pikey1967:
A bit harsh when it was purchased from Telstra under the understanding that I could use it on any network.

I am not really up on all this flashing and ROM stuff, so I think I might return the phone and write it off to a bad experience....to be honest for all the basic stuff the iPhone rocks....it was only due to the fact that we had blocked the iPhones from syncing with email at work that I thought I would give WM6 and HTC another try.

Came from the HTC Touch to the iPhone

Would love to flash the phone to the basic unbranded software, but the phone is only 4 hours old and I don't want to loose the warranty or brick the phone
[Touch HD General] Psygnosis84:
i think your at a good stage since the phone is brand new, flash it and hope for the best.

If you brick, take it back to Telstra demanding that the phone just died and you want your money back.

Seriously your going to miss out on a good thing, don't let Telstra screw it for you.

Flash a new ROM and call it a good year.

iPhone is made for idiots dude, don't stoop to that level.

by the way, wasn't there something called HardSPL that prevents bricking?
[Touch HD General] eaglesteve:
iPhone is a good choice if you don't need GPS,if you're not a heavy user who must swap in spare battery during the day, and don't need to read and create/edit office documents.
[Touch HD General] ZeeRocK:
G'day!

Thats the reason I never get into any sort of contracts , rather save money and buy an unlock unit. 4 yrs ago I paid off my Optus contract and since then bye bye to all the phone caps and contracts.

Wife's got a I-TOON its perfect for my 16 months old who cud take snaps of floor and carpet by just pressing the only button he can press. :D
[XPERIA X1 General] anaadoul:
Ok XDA, i have one big/huge/enormous problem,

Scenario:

Talking on the phone, using the Wired Handsfree (which came with the phone), when i get another call (call waiting) the notification of the other call is going through the loud speaker! not only that, the ongoing is immediately routed the loud speaker, anyone near me can hear the conversation clearly!!!!!!

does anyone face this?

i checked it on 2 X1s, 1 black & 1 silver and it's there.

anyway to solve this
[XPERIA X1 General] webguitar:
same problem for me :confused:
[XPERIA X1 General] George Knighton:
I have a similar problem with a Parrok CK3100. The phone can't ever seem to decide for sure what speakers it's supposed to be using.

Sometimes I'll press the Voice Command button on the bluetooth device and the phone speaks out, sometimes the car speakers speak out.

I just don't know.

Annoying that the much, much cheaper E71-2 handles all of this with great aplomb, as did my Q9h.
[XPERIA X1 General] anaadoul:
any one else facing this problem people?

i started searching in order to get a clue,

the main thing i'm thinking is that it's caused the same way VOIP (including skype) used to behave using speaker phone!

what do you think?
[XPERIA X1 General] walk:
I have the same problem with a german x1. ROM R2A.

Is there any solution for this problem

thx

walk
[XPERIA X1 General] anaadoul:
Fixed

Bugs Fixes (Registry):

Sound is routed to the Loud Speaker when having a phone call and get a waiting call while using Handsfree

change the key HKCU\

ControlPanel

\SoundCategories\Ring\Speaker to 0 (default value = 1).

added to the wiki of X1
[XPERIA X1 General] George Knighton:
Thanks. I've changed that setting to see if it solves my problem, too. :-)
[MDA II, XDA II, 2060 General] vitezkoja88:
i have a wierd problem :D i had qtek 2020 with wm2003 and german rom, so i upgraded it to wwe wm6... it worked fine for a day, but msn refused to sign in so i installed windows live... since then it shows "no service" and phone and contacts apps fail to start but sms and gprs work fine...

i tried flashing it to wm6.1 and it works the same... i noticed one thing: after first upgrade, all data was gone but after this one all my sms and stuff (notes, etc.) were there... at this point i notice that there's one sms that can't be deleted or marked as read

also after every flashing, when i restart phonr, i get bunch of errors for apps that were in startup of previous wm...

when i checked device information, there wasn't anything standing for extrom version so i guess that's the problem but can't find any extrom upgrade files :|

thanks in advance :)
[MDA II, XDA II, 2060 General] ferdiebaq:
Which version of WM6.1 did you install and did you follow all instructions when installing?
[PDA2, XDA IIi, 2020i General] martalegawa:
greetings, guys....

i got my self SRS_WOW_HD driver for my alpine from www.pocketpc-live.com

the problem is whether my english is not good, or it just doesn't set right. the volume is set to middle, can not set to max, and my alpine hangs.

had to hard reset it to be bcak to normal

anybody had it in their alpine?

please kindly give my poor self a step-by-step to do it
[PDA2, XDA IIi, 2020i General] martalegawa:
hellooo...:cool:
[PDA2, XDA IIi, 2020i General] sonus:
Don't install it, it muddies up the sound. If you connect your phone to an external amp, you'll see notice that the sound becomes garbled very quickly when you are running SRS_WOW. Furthermore, the only way to reset your sound back to original will be to do a hard-reset, as turning off SRS_WOW or uninstalling it leaves your sound even worse off than before.
[PDA2, XDA IIi, 2020i General] martalegawa:
thanks for the info.:)

before i posted this,

i did what yout tell me NOT to do

and the result is things you tell me that will happen if i do;)

o well i might have just stick with the treble-ly sound of my Alpine
[PDA2, XDA IIi, 2020i General] kamisaematsu:
SRS_WOW Not compatible for Alpine :(
[Touch HD General] Plonker:
Very informative, thanks. :)
[Touch HD General] spzero:
cool info, thanks for your effort.

but does this mean we may be able to improve drivers for a multi touch on our h/d or on other resisitive screens?
[Touch HD General] Major_Sarcasm:
This whole lack-of-multi-touch-on-the-HD thing got me thinking. One problem is obviously the gaming side of things, where you can't push two virtual buttons at once to go at a diagonal say.

If you open up an SMS and use the Transcriber option, then push at two points on the screen, there is a line drawn that stops mid-way between the two pushed points.

Would it not be possible therefore, for a cleverer person than I, to program a virtual D-Pad that could work out when two buttons were pushed simply by triangulating the position of the virtual cursor?

Does that make sense?
[Touch HD General] Meza1:
That's an interesting point, Major.

Try this also, in the notes app - turn it to drawing mode. Then hold one finger on the screen in one position, and then tap the screen or drag around the screen with your other finger. You see how the touchscreen makes lines that fan out between the two points of contact.
[Touch HD General] tazbo28:
i believe that it may be possible to somehow utilize the fact that something does happen when pushing in on two points of a resistive screen.

the real problem with it is that when you push on two seperate points, the screen makes an indentation that spans across the area between the two. the layer you are pushing on is simply not elastic enough to register two smaller seperate points or indents. its just read as one big indent on the layer between the two points of pressure. this is why the the screen only reads a point between the two. the sensor is just picking up one giant blob that centers at the mid point between your two fingers. this wouldnt really help much because the farther apart your fingers are the more random the point location becomes---this is because the thin layer will be contacting the layer below at multiple random spots between your two fingers. idk. it seems like it wasnt meant for multi touch. and a driver would need to have a more precise input than that.
[Touch HD General] Major_Sarcasm:
Ahh, but consider a simple d-pad arrangement, with 4 direction buttons and maybe 2 action buttons (à la SNES or similar?). Diagonals would be easy enough with the point of contact appearing between the 2 buttons pushed. A move-and-fire combo could be detected with clever placement of the virtual action buttons giving the device a good clear area of detection.

If I get time today, I'll try to draw a simple graphic. A picture speaks a thousand words and all that.

Edit: OK, excuse my laughable drawing, but you get the idea. With better placement, the buttons could be made quite in-sensitive to where the fingers/thumbs are pushing on them.
[Touch HD General] Caid444:
My thoughts on the matter.

I think it would do emulator or even virtual d pad developers well to add this option into their d pad. When you press on two points the screen reads in between right? So if you're playing mario and you're trying to run and jump over a hole, just have a setting that allows right button to continue if suddenly the pointer reads in the middle of the screen. In otherwords, it would make no sense for a nintendo player to suddenly press the middle of the screen, so the d pad would read that as a whichever butten first pressed, plus button now being pressed.

If it reads exactly between both points, then the software should be able to guess which button you're pressing by calculating which buttons are exactly in line with eachother. There will be a beginning reference set by the first point pressed, so it is only a matter of auto executing o---^---0. I hope this idea makes some sense to someone other than me.

Just think of Orion's belt and it's symetry to get the right idea of what I'm talking about.

Caid.

Just a bit more clarity, if the d pad developers set up a reference of center screen points, the could technically program their pads to be multitouch souley off the basics that each two buttons pressed together would have a center point at an exact or near exact point in between the left and right side of the d pad. This wouldn't work for diagnal, but for any direction plus ABXYLR there would be a center point between each of them, a place in between them that the phone would register the touch.

Is this exploitable?

Sorry for constantly editing, but ideas keep crystalizing.

Beyond the first idea, to register an A+b, have slide vs tap settings on the d pad. That means, if I slide from a to b, the d pad will hold a and activate b as opposed to just switching between the two. Once again, this should technically be possible with the first idea as the middle reference point should also read a shift. In fact, if you're pressing on both sides of the screen at once (d pad and abxy) then all the actually pressing action would be happening in the center of the screen or rather between both pads.
[Touch HD General] vangrieg:
I seriously doubt that it's technically any more difficult than calculating the two touch positions on a capacitive digitizer (keeping in mind that in reality "multi" means "dual").
[Touch HD General] chaosdefinesorder:
it's actually hysterical raisins (historical reasons) that resistive is single touch only - when PDAs were first developed, the designers had to cater for both stylus (very precise) and finger use. Finger use is spread over the fingertip so the designers hard-coded algorithms that would average out the touch coordinates so the middle of the touch events.

The mentality basically went along the line of "why would you want to touch two points on the screen at the same time? Nothing uses that! Can you think of a use for that? No? Ah well, we don't need that then"

This has held until Apple decided to use the more battery draining capacitive method (resistive only uses battery when the two layers touch, capacitive has a constant charge and therefore constant drain) and decided to use multi-touch as a gimmick (and, lets be completely blunt here it IS a gimmick - pinching is NOT easier than running a circle around the point of interest and it's certainly more clumsy than a slider for zooming!) under the pretense of a new and awesome feature for mobiles (it does have practical use in laptop trackpads though)

Resistive technology does support multi-touch, but it's a bigger issue to code the function because the touch events are processed by the touch controller then sent to the operating system as x/y coordinates. The operating system can't do anything about this. To get resistive technology to support multi-touch you'd have to re-code the controllers...
[Touch HD General] montag09:
Major_Sarcasm and Caid444, I agree 100%. If I just had the time, given that I can develop applications using .Net Framework, I should be able to replicate this in a simple application. Will try and get back to you... I'll start with a Win XP app, just the concept, and then I will deal with Compact Framework (if it's still called 'Compact'). Making drivers to work in any application is another story, though.
[Touch HD General] orb3000:
Thanks tazbo28

Very usefull info here!
[Touch HD General] Eraser85:
Here what the guys working on android have been able to produce with a capacitive screen:

http://gizmodo.com/5097166/android-multitouch-proof-of-concept-aint-pretty-but-it-works

Multi-touch that works "not-so-well-but-at-least-it-does"
[Touch HD General] gadgetuk437:
Your source?
[Touch HD General] Caid444:
I don't think so...

Just a little comment about the two points creating a crease down the screen. The distance between the metalic layer and the plastic screen is minimal at best, not to mention the material on the top layer is very flexible. I don't think it's likely at all that the screen would have a crease or ridge between the two points, there's just not enough indent to create this scenario.

One more thing, I'm not 100 percent sure, but I get the impression that the space between the two layers isn't actually filled with air but in fact some sort of non conductive fluid or gel. It would help the two laters to retain their space and elasticity from eachother.

But what do I know without poking holes in my screen (and I'm not about to do that.)

Caid.
[Touch HD General] tazbo28:
just got this from wikipedia

Resistive touchscreens are composed of two flexible sheets coated with a resistive material and separated by an air gap or microdots. When contact is made to the surface of the touchscreen, the two sheets are pressed together, registering the precise location of the touch.

For example, during operation of a four-wire touchscreen, a uniform, unidirectional voltage gradient is applied to the first sheet. When the two sheets are pressed together, the second sheet measures the voltage as distance along the first sheet, providing the X coordinate. When this contact coordinate has been acquired, the uniform voltage gradient is applied to the second sheet to ascertain the Y coordinate. This operation occurs instantaneously, registering the exact touch location as contact is made.

Resistive touchscreens typically have high resolution (4096 x 4096 DPI or higher), providing accurate touch control. Because the touchscreen responds to pressure on its surface, contact can be made with a finger or any other pointing device.

the part about "microdots" is true i can see the grid of super tiny dots on my 8125 touch screen
[Touch Diamond, MDA Compact IV ROM Development] f810:
Hi,

My Diamond has no response on the screen, so I think I need to return to factory for repairing. However I have difficulties in falling back to stock ROM and SPL.

From the Wiki:

---------------

STEP BY STEP HOW TO RETURN TO STOCK SPL - FOR WARRANTY REASONS ONLY!

0. be sure to first restore stock OS, and stock radio. stock SPL is always to be done last!!

...

-----------------

I can't flash my ROM to latest HK WWE CSL ROM (2.03) as it just stopped at 0%. I'm using SPL-1.30.OliNex.

Questions:

0) Why? Any step I've missed? I've just copied the .NBH from HTC official ROM download. Should I get the .NBH from the Wiki instead?

1) Should I flash to v1.93 (the very beginning of the ROM)?

2) Must the RADIO be flashed back as well? or the above Stock ROM has included the RADIO already?

3) Anyone can give me a reference on the step-by-step in details...

Thanks!

Please help...

F810
[Touch Diamond, MDA Compact IV ROM Development] R3PUBL1K:
Questions:

If the latest was the offical from the site then you could use that - as you are having issues flashing this with 1.30 HSPL, I would suggest updating that to 1.40

This might be a easier option and should work woth the 1.30 HSPL

This is recommended

Its really straight forward like the WiKi suggests :D

This Thread may help
[Touch Diamond, MDA Compact IV ROM Development] f810:
Thanks a lot.

Re Q3, so do you mean if I extracted the stock NBH, it's only OS but not including RADIO? If so, I will get the RADIO from wiki page later. Would you please clarify for me?

After your information, I think the steps in Wiki are clear. Thanks.
[Touch Diamond, MDA Compact IV ROM Development] R3PUBL1K:
If this is HK ROM is the one you have downloaded from HTC PAGE then it has a radio included
[Touch Diamond, MDA Compact IV ROM Development] f810:
Since my Diamond is totally malfunction in the touch screen, I can't response to all the confirmation & prompts...

I've failed to install Stock ROM and tried your recommendation on upgrading to HSPL 1.40. There was a confirmation on running the program in my Diamond and I can't press YES and now my diamond is just like bricked.

I've also tried pressing VOL DOWN + Reset to connect the Diamond via USB. The ROM Update Utility has "successfully" update the HSPL, but actually when I hard reset it and found it's still running 1.30... Can I just use this approach to fallback to Factory status??

Anyone has good idea on how to fallback to Factory Stock ROM, RADIO and SPL, provided that my screen has totally no response to me?

PLEASE...PLEASE...PLEASE help.

:(
[Touch Diamond, MDA Compact IV ROM Development] R3PUBL1K:
You will not be able to update olipros Hard SPL in bootloader mode as the SPL is protected and the 1.30 will prevent this although show its been done.

What you will need to do then is just load a 1.93 ROM from boot loader. the were some in that link i posted earlier. as to reverting to the default SPL - you may be luck not to need the screen for any confirmation. but running a new SPL to overwrite Oli's you will need to use windows and the RRU
[Touch Diamond, MDA Compact IV ROM Development] f810:
I've tried to load 1.93 ROM to my diamond but failed on OliNex 1.30. The link in modmydiamond.info on OliNex 1.40 Signed seems not correct, as it's still 1.30 after flashed. I've then flashed UNSIGNED 1.40 OliNex SPL (also downloaded from modmydiamond.info) and now flashing the 1.93 ROM in progress from bootloader.

I will flash the Stock SPL through the Bootloader after that...I hope I can successfully fallback and get it repair...

Last question (I hope), the stock SPL should be 1.37 so I want to confirm whether it can boot 1.93 ROM.

Thanks a lot!
[Touch Diamond, MDA Compact IV ROM Development] band27:
Because these Unsigned HARD SPL 's are write protected.....you will fail all the time. Not sure if stock SPL can undue the write protection but if you still get stuck after you try then in order to bypass write protection I know Jump SPL allows for this.
[Touch Diamond, MDA Compact IV ROM Development] f810:
you're right. When I flash the Stock SPL, it is "successful" but actually it doesn't update the SPL (i.e yet running OliNex 1.40). Where can I get the Jump SPL?
[Touch Diamond, MDA Compact IV ROM Development] band27:
Here you go....I did a search :)
[Touch Diamond, MDA Compact IV ROM Development] kawatsu:
Hi,

Sorry to use this thread but im also trying to install back to my original Diamond ROM and am currently using the rom developed by Diamond Project (1.93.456.2WWE) and i kept flashing it back using Signed V1.93 RUU and apprently the Diamond project words still keep showing out when i start my phone!

How do i completely remove the Diamond Project thing? Thank you!
[Touch Diamond, MDA Compact IV ROM Development] band27:
Read this............Scroll to Post #39

http://xdaforums.com/showthread.php?t=400950&page=4
[Touch Diamond, MDA Compact IV ROM Development] f810:
I also got that but it's not win32 program... I believe it's running on the Diamond. But I've hard reset, and never able to setup as it's screen was not functioning now...

:(:(:(
[Touch Diamond, MDA Compact IV ROM Development] R3PUBL1K:
That ROM had a different boot image - so you need to replace that by flashing another splash .NBH file using RUU.

Original splash can be found HERE

and if needed CUSTOM RUU HERE

Just un-zip these and put the splash file in the same folder as the Custom RUU and run the RUU - the flash should take a few seconds and viola - bye bye Diamond project splash. :D
[Touch Diamond, MDA Compact IV ROM Development] R3PUBL1K:
I think as long as the SPL is changed and the ROM is of the original language the I think it should be OK to send back like that
[Touch Diamond, MDA Compact IV ROM Development] R3PUBL1K:
As said before; you should be able to successfully run the stock SPL using RUU - if you are trying this via bootloader it will not work.
[Touch Diamond, MDA Compact IV ROM Development] Scann69:
Which is the original SPL?? 1.23, 1.34 or 1.37? I do recall taking a picture of the original SPL when i 1st got the Diamond for days like that but i just can't find it now :(

I'm bought it from Malaysia. Anybody can help me confirm this??
[Touch Diamond, MDA Compact IV ROM Development] f810:
I've tried to connect to ActiveSync successfully although the Initial Setup wizard on my Diamond. I've then run the RUU from RUU-SSPL-withoutNBH.zip and put the stock SPL .NBH file into the extracted directory. It can retrieve my device info, and when I confirm the update of ROM, after 3-5 sec it said about connection failure. I can browse the Internal Storage at the moment yet.

I've then tried similar thing using the Custom RUU inside the package diamond-hspl-1.34.zip. This time I can see 100% update. When I press VolDown and reset, the SPL is still v1.40 ONliEx.

What's wrong with my procedures above?
[Touch Diamond, MDA Compact IV ROM Development] f810:
I think I miss the step of running the SSPL-Manual.exe because of my screen is not responding... Anyway for me to put it into the Windows Startup Folder?? When I use ActiveSync I can't see Windows directory.

Please...please...I miss this step only...
[Touch Diamond, MDA Compact IV ROM Development] f810:
Can anyone help??
[Touch Diamond, MDA Compact IV ROM Development] R3PUBL1K:
try this - Unzip and run the RUU for flashing olinex 1.93
[Touch Diamond, MDA Compact IV ROM Development] f810:
Thanks! Will try it tonight. :)
[Touch Diamond, MDA Compact IV ROM Development] f810:
No hope and just got connection error though I have connected the Diamond thru Mobile Device Center.
[Touch Diamond, MDA Compact IV ROM Development] R3PUBL1K:
This certainly does work - Not sure why you PC states it can not see the device although WMDC is connected?

Did you restart and try again.
[Touch Diamond, MDA Compact IV ROM Development] f810:
I'm using Vista and trying to use WinXP now... :(
[Touch Diamond, MDA Compact IV ROM Development] f810:
Actually this is the same symptom when I tried to update the stock SPL using RUU.
[Touch Diamond, MDA Compact IV ROM Development] f810:
Same connection error using WinXP. Shouldn't be PC issue...

If I put the stock rom to Internal Storage and flash directly, is it possible to overwrite the SPL as well?
[Touch Diamond, MDA Compact IV ROM Development] f810:
I've tried on my wife's Diamond using the Wiki approach, the RUU worked great to restore the Stock SPL. The different between the workable Diamond and faulty Diamond was mainly the enterbootloader program requires confirmation to run. The faulty Diamond cannot prompt & let me confirm the enterbootloader program...

Anyway for me to put it in startup program with parameter to answer it as 'YES' without prompt??