yashsingh1/xdaforums huggingface dataset:
[MDA III, XDA III, PDA2k, 9090 General] man31:
I would like to know whether the parts of my i-mate pda2k are the same with O2 XDAIII parts.. I want to replace the casing of my imate pda2k as well as the keyboard.. I am just planning to buy defective O2 XDA III to replace some parts on my imatepda2k.

Do all the screws, fittings, external and internal parts of imate pda2k same with O2 XDA III?

and the O2 XDAIII the same with O2 XDAIIs? they do look the same.. :D
[MDA III, XDA III, PDA2k, 9090 General] egzthunder1:
You should look in the wiki, you will see all the possible name variations for the BA. If I am not mistaken, the only thing that may change between models is having a camera (or not like the SX66). The only BA-type device that will have a difference is the Harrier (CDMA version of the BA) which has a few more important differences.
[MDA III, XDA III, PDA2k, 9090 General] Chef_Tony:
i believe there are actually more differences in the hardware specs, like two different displays or something and i do remember there was a table on the wiki and i know, whenever i look for it, i spend ages searching, i wanted to provide the link here, but actually, i cannot find it right now... again.
[MDA III, XDA III, PDA2k, 9090 General] egzthunder1:
True, but if he is only looking at the casing, he should not be concerned with anything "under the hood". As long as the case is the same, he will satisfy his needs.
[MDA III, XDA III, PDA2k, 9090 General] man31:
actually i am planning for to get the casing of a defective O2 xdaIIs, which similarly looks the same with the imate pda2k.. will i succeed with this one?:D
[Tilt, TyTN II, MDA Vario III General] Areinu:
I think it's my fault because I used my kaiser in moist enviroment. (little rain) Afterwards after sliding I would hear sliding sound few times as if I would quickly slide in/slide out and my keyboard was quickly blinking.

I turned the phone off and let it dry. This fixed the blinking.

But first it went during use from 9x% to 2x% in few seconds, then last 20% drained pretty quickly too. I charged it and it went to 100% then did the quick drop again. I decided I would let it drain completely and then try charging it. Now it charges only until 37%. The charging icon is there in my WinMo, so USB probably works well.

Other than that sliding the phone in or out doesn't register at all in WinMo. I can live with that because I always set winmo to use only landscape orientation anyway. Too bad I don't have autounlock/screen on when sliding out anymore.

So, anyone has an idea how to make the phone behave as it should? I have screwdriver that I used with SPV C600 long time ago and I think it used the same screws, so I can get into my phone if neccessary and if fix is simple enough.
[Tilt, TyTN II, MDA Vario III General] dcarr622:
At least try a new battery if you can and see if that corrects the problem. Ironically, though, after one of my HTC's got submerged in water, the battery was the ONLY thing that worked everything else was shot.
[Tilt, TyTN II, MDA Vario III General] Areinu:
Well, my friend has Kaiser as well and I was playing to test out each others battery, but I won't see him until Wednesday or so. Anyway, now it's stuck at 25% max, when it was 37% it lasted for about 2 hours. Even though I was reading e-book and listening to music, writing SMSes and it was on train so it probably often changed the towers. When I could charge it to max it obviously worked a lot longer. I usually charged it once every 2 days.

And I didn't think it was that bad weather. It was just mizzle, if dictionary tells me right, so only keyboard got wet afterwards. I didn't think it would affect insides. Anyway, I'll keep you informed on the experiments after Wednesday. If other battery will work without problem I'll just buy new one.
[Tilt, TyTN II, MDA Vario III General] Mr. Clown:
You are right, It happened to me with my first kaiser. I spilled milk on it and the only thing that worked after was the battery:D

Kaiser dying very slowly ;)
[Tilt, TyTN II, MDA Vario III General] Areinu:
Ok, I tested it just now.

I charged my phone overnight. It was 25% when I woke, 8% when I got to my friend. I put my battery into his phone. It showed 90%.

My friend's battery was at 80%. Put into mine it showed 1%.

So it seems my phone can now see only last 20% or so of the battery. It's... not good. It means I have to fix the phone somehow. Now any ideas how? Later today I'll open it and try to find things out of ordinary and I'll make photos of them if I won't know what to do.
[Tilt, TyTN II, MDA Vario III General] Mr. Clown:
Try to clean your battery terminals and see if that can help... http://xdaforums.com/showthread.php?t=358136
[Tilt, TyTN II, MDA Vario III General] Areinu:
I tried cleaning terminals before, didn't help. But I did thing described in 1st post of that thread. Today my battery maxed out at 12% no matter how long I would charge. The thing at first post made 45% detectable, which... is at least much better than 12%. Or 25%. Or 37%.

I've tried getting into the Kaiser yesterday but the screw under the speaker is stuck and halfway stripped and I had no luck trying to unscrew it. But it might not be necessary after all, if the method from that post helped in getting to 45% then maybe playing with the battery more will help. There's more methods in that thread, I'll try them out later.

Well, thanks a lot for the link. Now I'm getting hope back :D
[Tilt, TyTN II, MDA Vario III General] Areinu:
Ok, here's the update.

Now the phone is running at about 32% juice max and no matter how I play with the battery it won't go above 32%.

When it's on 1% it lasts on it for quite a long time. Like 20-30 minutes. Then the phone turns off.

When I try to turn on the phone then it goes trough the screen with radio etc. then htc logo and turns off when windows would have started. No matter how many times I try to turn it on then it will do it like that. So, my theory is windows has some kind of energy saving feature that makes it turn off when it detects it's like 0.5%. I wonder if there was a way to make windows not turn off no matter what and if then maybe I could use 100% of the battery even if 68% of it would be on 1%. Of course it's just my idea and might not work. I don't know how kaiser checks the amount of power left and if my kaiser can get power from the whole battery even if it can't measure it well.

I wonder if android might work well?

I'm thinking about software solution because I can't go trough the broken screw below the speaker. I went to a shop to see if brand new screwdriver would manage to unscrew it, but even it slipped out(new screwdrivers are usually not curved at the edges so sometimes they work). I have no idea how to remove the screw.

Ah, when it turned off and it was turning off at windows I played with the battery and managed to turn it on with 3%. Well, even with additional 3% it was only like 3.5 hours of use at most from 32% I had at the begining.

So to sum it up:

do you think a software solution is possible?

do you have any ideas how to get rid of that screw without damaging the phone?
[Tilt, TyTN II, MDA Vario III General] Flying Kiwi:
Not if it's a hardware problem causing all the symptoms. Besides, you wouldn't be able to flash with less than 50% battery charge registered (don't know if microSD card flashing has this requirement as well but I wouldn't do that anyway).

Your comment earlier about screwdriver edges being rounded off makes me wonder if you're using the right screwdriver to begin with. You do realise they're torx screws which are meant to be removed with special Torx screwdrivers don't you? If you have failed using the correct tool for the job then you could either try glueing the driver into the screw head and letting it set for a couple of days (being very careful not to get any gue anywhere else other than inside the screw head cavity). There are also devices called screw extractors or easy outs which require the head of the screw to be drilled down the middle first. I've used this technique with success in the past on a much bigger scale but I don't know if they go down small enough in size to suit these phone screws - you might want to talk with a jeweler to see what your options are. You'd also need to tape a plastic bag all around the screw to protect the rest of the phone from swarf if this method is possible/necessary. I think the phone is going to need opening up to get to the bottom of the problem as my first thought of cleaning the battery terminals has already been tried (assuming you did it thoroughly with some contact cleaner on the end of a cotton bud).
[Tilt, TyTN II, MDA Vario III General] Areinu:
I know about torx screwdrivers and I removed all Torx screws I had to go with, but under the speaker is single cross screw meant to be removed with Thompson screwdriver. If you look into confidential service manual(this forum links in few places to it :P) it tells you you need few screwdrivers for the job. Well, I assumed those extractors that require drilling the screw are mostly for bigger ones, like in cars etc. This one is pretty small. But I'll try with the glue, it's probably big enough for glue to catch on without me gluing the screw to the phone which would be a disaster.

It's why I suggested Android. With haret you don't have to flash to boot it. And I actually did it and am trying to run out of the juice since yesterday(Wifi always on etc). While WinMO says it's 3% android says it's 30%, and it goes down slowly like hell. But it's for sure hardware problem so I can't see why android would be able to use whole battery -.-; I am trying to get phone to lose all energy, then I'll see how high it will charge on android(for now it didn't charge past about 50% but as I said it goes down very slowly).

As for flashing, it usually doesn't take that long at 50% figure is just for safety. But before attempting to flash I would start with hard reset, probably would fix most of things flashing would.

Anyway, as for the screw, it's easter and I'm at family house, I didn't take my tools or anything so it will have wait till I'm back.
[Tilt, TyTN II, MDA Vario III General] Flying Kiwi:
Sorry, mine has the Void sticker over it and I just assumed it was Torx like the rest.

You'd still need a reliable boot loader to load anything though and from the sounds of it, you don't have that.

I can't see why Android would offer a 'solution' given it's a hardware problem which presented itself after your phone was rained on.

The flashing program wouldn't let me progress when I tried it once before and although the flashing process is much shorter than it would normally take to use 50% of your batteries power, the current consumed during the process is higher than during normal operation and it's important that the voltages don't dip below acceptable values when writing to the EEPROM/Flash Memory. Much better to start by fixing the hardware issue and then sorting out any possible corruption in the EEPROM afterwards once the battery is fully charged.
[Tilt, TyTN II, MDA Vario III General] Areinu:
Wednesday. I tried getting rid of the screw again. Failed. But I got inside. I realized(and called myself an idiot over and over again) that the screw only held that small board next to sound controller connected to phone, but I could still proceed to open it. Anyway, I got inside.

I looked around for things out of ordinary. There was some dust here and there, but nothing serious. Except for this:

What, wait, isn't that mold? It seems like it is... Well, I cleaned it all off. Furthermore I got rid of most of the dust, as I was inside already, checked connections here and there. General maintenance.

After turning on the phone:

- Slide in/Slide off works

- WinMo showed 77% and it's probably right. I charged it fully on android then used for enough time to get ~25% down.

After using it for a bit the phone froze. I restarted it and WinMo was showing 3%. I realized I didn't press the casing to the keyboard hard enough so there might have been some elements loose. Another restart and it shows 76% again. Well, let's see how far it will charge.

Update: It charged with normal speed to 100%, and both WinMo and android agreed on it. Case solved, I guess.
[myTouch 3G, Magic Themes and Wallpapers] Taknarosh:
I made a custom boot animation and would like to know how to pack it into a update.zip to be applied via recovery.

I've applied it myself to my own phone but for the convenience of people prefer recovery update method.

Dirty Preview: (Real One is in much better Quality)

Youtube Video: (Sorry for the bad quality didn't have my camcorder on hand)

http://www.youtube.com/watch?v=CC0xF21Gjqk

Would anyone be interested?
[myTouch 3G, Magic Themes and Wallpapers] dreamsofubuntu:
Very nice =]
[myTouch 3G, Magic Themes and Wallpapers] thatruth132:
i think this might help

http://ostebaronen.dk/change-the-second-boot-screen/
[myTouch 3G, Magic Themes and Wallpapers] cten1:
man the boot logos are looking better and better!

pretty legit though
[Hero CDMA General] gmelchert:
I know all the hype for sprint right now is the nexus one and supersonic.. but I'm just curious, do you think that the monthly plan for the Supersonic is going to be more than the current $69.99-$99.99 for the hero? I know it is for the little 4G Hotspot brick thing ($60 I think)

I sure hope it isn't... tell me what you think!
[Hero CDMA General] orris:
I say they'll start out with a 5-10 dollar add-on fee for current plans 69.99 and up and see how that goes over. I don't believe that people will pay much more than that for it.
[Hero CDMA General] Sporkman:
idk i think it people who have no 4g service should not have to pay any extra till its in the your area imho
[Hero CDMA General] rkendle53:
the 4g data plan is the exact same price as the 3g plan, most ppl think its more becaue they have grandfathered plans that are cheaper, and the supersonic will use the same 69 - 99 dollar plan codes as all of our smartphones. this is written in stone, think about when the switch from 2g to 3g happened... prices were the same because of the way it was deployed.
[Hero CDMA General] frostrunner:
4g is an unlimited service where you can get it^^ doesnt have a cap on how much you can use
[Hero CDMA General] gmelchert:
that sounds correct (or should be) glad to hear it. :D
[Nexus One Q&A, Help & Troubleshooting] alwnan:
Hi guys, my phone currently running Amon_RA 1.6.2 and CyanogenMOD 5.0.5. Now I want to upgrade to Amon RA 1.7.0 and CyanogenMod 5.0.5.1. I know how to upgrade the ROM and I can use the updater to do that, but do I upgrade the recovery image first? and how do I upgrade the recovery image?

Thanks
[Nexus One Q&A, Help & Troubleshooting] david1171:
No you do not have to update the recovery image first and

fastboot flash recovery [path leading up to recovery image]/[name of recovery image].img

i.e.

fastboot flash recovery C:/recovery.img
[Nexus One Q&A, Help & Troubleshooting] alwnan:
Thanks I just figured it out, and realized it was a dump question to ask...
[HD2 Windows Mobile 6.5 ROM Development] appelflap:
Anyone build a rom with wm 6.1 for the HD2 ? What were/are your experiences?

Does sense 2.5 run on wm 6.1?
[HD2 Windows Mobile 6.5 ROM Development] curiousGeorge:
Wow, I honestly thought this was a misplaced question. I don't know of anyone who goes back and cooks OLDER roms. I'd think there'd be some sort of technical difficulty in getting programs designed for the newer system to work with an older one (though it's not so often the other way around).
[HD2 Windows Mobile 6.5 ROM Development] appelflap:
I've read some posts from tp2 users who reverted from 6.5 back to 6.1 and they said it was much faster. So as curious as a appelfap can be :) I asked my self the question how fast 6.1 would be on a HD2?

The question is which OEM base should be used for that (can the multitouch driver be used etc) and which EXT packages will run on it (I guess only sense 2.1)
[HD2 Windows Mobile 6.5 ROM Development] KB24@CL:
I'm not sure it can get "much faster" since its already close to "instantly".

With that said 6.1 is absolutely not finger friendly, nor does it support multi-touch-gestures...I'm really not sure anyone has any interest to cook such a rom especially since probably only VERY few people have interest because they want to use a certain app which has compatibility issues on 6.5 or something...

so to be honest, if speed is the only reason...then its not worth it since HD2 is blazing fast as it is right now.
[HD2 Windows Mobile 6.5 ROM Development] NRGZ28:
Come on man.. how much faster do you want to go ? LOL

Like KB24@CL said.. the HD2 is already INSTANT. 6.1 is a fugly POS compared to what we can do with 6.5 and the HD2 is alll about looking good. :p
[HD2 Windows Mobile 6.5 ROM Development] arifqur:
You said it man and in my, and a lot of people's opinion you Absolutely Rule on Looking Good

A very big fan of you NRG
[HD2 Windows Mobile 6.5 ROM Development] dudu7559:
NRG is right, cooks have been developing ROMs for ages and a request like that one is supposed to be weird, at least, just because we're used to looking ahead and not to drawing back.

Apart from this, most of the electrical components have no 6.1 drivers and they could get back an unpredictable reaction............. I think we shouldn't read so much into those matters, but WM is supposed to go ahead........... forever. :)
[HD2 Windows Mobile 6.5 ROM Development] appelflap:
Whatever :p:) I'm going to try it, just for fun.
[HD2 Windows Mobile 6.5 ROM Development] ~~Tito~~:
I don't think there is an official WM 6.1 ROM or cooked 6.1 ROM. So you cant try it.
[HD2 Windows Mobile 6.5 ROM Development] appelflap:
Are you serious? Now that would be a real constraint :)

Btw what about a good old ce 2.0 :) with a good looking desktop...
[HD2 Windows Mobile 6.5 ROM Development] dwizzy130:
Have you ever cooked a ROM? All he has to do is grab a WVGA WM6.1 SYS and XIP and throw it into a kitchen. Only things I can think of that may halt this is the lack of 6.1 drivers (multi touch, etc...) and whether a 6.5 OEMXIPKernel would work with 6.1.

dwizzy130
[HD2 Windows Mobile 6.5 ROM Development] appelflap:
Yep, found a WVGA WM 6.1 SYS 21056 version over here
[HD2 Windows Mobile 6.5 ROM Development] Ultimaex:
kwbr produced a 6.1 rom when the leo came out and sspl was released. look for topix rom. i dont know if it is still linked in the thread!
[Dash 3G, Snap General] leonem:
Is there a way of changing the start menu icons on HTC snap to something that is not as pixelated as the current one? I have looked all over but have found no solutions.

BTW, I'm new to windows mobile (3 days old) go slow if you are giving me any instructions
[Dash 3G, Snap General] mattyrs500:
AAAAAAA i need help too

I have been looking for over 3 hours to try to find out how to change the icons with not luck. If anyone knows please help. I created a skyfire shortcut on my start menu that goes straight to my favorite site(google) but i cannot find out how to change the icon from the skyfire S to an actual logo
[Dash 3G, Snap General] leonem:
search

3 hours? I have tried to get this for 3 days... even contacted HTC customer care... let me hope they do something about it
[Windows Mobile Development and Hacking General] scilor:
I am currently working on my "SciLor's WiMoBlue". The new protocol is ready. Everything works fine, until I send much data at the same time.

For example if I try to send an image in that way:

Public Sub SendImage(ByVal Image As Bitmap, ByVal Position As Point, ByVal Format As ImageFormat)
Dim PosX, PosY, Width, Height As Byte()
Dim ImageStream As New IO.MemoryStream
Dim ImageLength As Integer
Dim ImageLengthBytes As Byte()
Dim ImageBuffer(MaxChunkSize - HeaderSize - 1) As Byte

PosX = BitConverter.GetBytes(Position.X)
PosY = BitConverter.GetBytes(Position.Y)
Width = BitConverter.GetBytes(Image.Width)
Height = BitConverter.GetBytes(Image.Height)

Image.Save(ImageStream, ImageFormat2ImagingFormat(Format))
ImageStream.Seek(0, SeekOrigin.Begin)
ImageLength = ImageStream.Length
ImageLengthBytes = BitConverter.GetBytes(ImageLength)

SendData(BuildCommand(BaseProtocol.Image, ImageProtocol.Initiate, CombineBytes(PosX, PosY, Width, Height, ImageLengthBytes)))
Thread.Sleep(2000)
Dim DataPos As Integer
For DataPos = 0 To ImageStream.Length - MaxChunkSize - HeaderSize - 1 Step MaxChunkSize - HeaderSize
ImageStream.Read(ImageBuffer, 0, MaxChunkSize - HeaderSize)
SendData(BuildCommand(BaseProtocol.Image, ImageProtocol.Data, ImageBuffer))
'WaitForNextChunk = True
'Do While WaitForNextChunk = True
'Loop
'Thread.Sleep(2000)
Next

ImageBuffer = New Byte(ImageLength - DataPos - 1) {}
ImageStream.Read(ImageBuffer, 0, ImageBuffer.Length)
SendData(BuildCommand(BaseProtocol.Image, ImageProtocol.End, ImageBuffer))
End Sub

SendData:

If Data.Length > MaxChunkSize Then
MsgBox("Data to long... " & vbNewLine & "SendSize:" & Data.Length & vbNewLine & "MaxSize:" & MaxChunkSize)
Else
If btClient.Connected = True And isRecieving = True Then
btStream.Write(Data, 0, Data.Length)
btStream.Flush()
End If
End If

Recieving Part:

While isRecieving = True
If btStream IsNot Nothing And btStream.DataAvailable = True Then
Try
Recieved = btStream.Read(myHeader, 0, myHeader.Length)
If myHeader(0) = HeaderIdentifier And myHeader(1) = OtherModeHeader Then
btStream.Read(myDataSize, 0, 2)
DataLength = BitConverter.ToInt16(myDataSize, 0)

myBuffer = New Byte(DataLength - 1) {}
Recieved = 0
Do Until Recieved = DataLength
If btStream.DataAvailable = True Then
Recieved += btStream.Read(myBuffer, Recieved, DataLength - Recieved)
End If
Loop
ExecuteCommand(myHeader(2), myHeader(3), myBuffer)
Else
Debug.WriteLine("WrongData")
Exit While
End If
Catch ex As Exception
Debug.WriteLine(ex.Message)
If Recieved = 0 Then
Exit While
End If
End Try
End If
End While

If I send the image, without Thread.Sleeps (huighe ones). The recieving stream gets weird. The gets btStream.DataAvailable = False forever. If I remove that ckeck, it hangs at the btStream.Read.

I also tried to fix that with waiting for the answer of the server, but the problem doesn't get solved.

Do you have any idea how to fix that problem?. In that speed the image sending is worthless :(

SciLor
[Touch Pro2 CDMA] tonefour:
I've upgraded to WM6.5 and although sense is nice, I have found reason to disable it (I'm not gonna elaborate as this leads into a new thread about the WM6.5 upgrade).

Anyways, I don't have Sense activated, but I do want access to HTC calendar and HTC alarm. Those two things are still by far better interface and look than the WM stock (which sadly WM 6.5 still does not improve).

Is there anyway to direct a link via parameter of some sort to the HTC versions of calendar, alarm (and possibly other features like text messaging).

I've been looking for extracts of the two and nothing.

I've tried replacements. ThumbCalendar is pretty good replacement for the HTC calendar, but it's kind of excessive in features and not free.

I've tried many alarm programs, like g-alarm and klaxon. Both fail at being extremely slow in actually setting up an alarm, and actual navigation and loading of the program.

any info much appreciated. thanks.
[Touch Pro, Fuze General] Jappuh12:
HTC Touch Pro

GMiC1000 ROM - First Dutch WM6.5 ROM![WM6.5.5|23542][Sense 2.1|2.5]

Hello,

Always when I press the symbol, sms/mms and that kind of special buttons on the keyboard it gives the error: PTTMOD.exe So I cant put symbols in a textmessage, email or tweet (big:() I have to reinstall it but I cant find a cabfile or something like that thats called like PTTMOD.cab Can someone please help me?

Jasper
[Touch Diamond, MDA Compact IV General] ATBT:
I have flashed my phone and it doesnt have the phone keypad input so i can use it for SMS but it has the qwerty keyboard. Can anyone tell me where i can download the keypad.

Cheers.
[Touch Diamond, MDA Compact IV General] mr.horndoctor:
Are you wanting the phone dialer or the keypad for text input?
[Touch Diamond, MDA Compact IV General] ATBT:
the keypad to input text. for example 2=abc 3=def etc...
[Touch Diamond, MDA Compact IV General] ATBT:
Nevermind, i found one.