yashsingh1/xdaforums huggingface dataset:
[HD2 Accessories] ialafroz:
I think this is a very serious problem that needs to be addressed to HTC if not done yet by someone, a friend´s apartment got caught on fire because a htc charger, same problem I assume , I guess we need to keep the charger on sight when in use to avoid a disgrace.
[HD2 Accessories] davidgiga:
I hope my old charger from my touch diamond will not have the same problem sometime
[HD2 Accessories] gamer-Kenny:
Same problem with the charger of my Xperia X1 (also HTC), smoke came out the charger.
[HD2 Accessories] Kalavere:
Ouch. :eek: I keep mine on a hardwood floor, but this time of year it's always a good idea to keep a eye on power packs and chargers. I've always thought my charger ran remarkably cool, I run a cradle off of my charger and frequently charge the phone and battery at the same time, I think I'll give it a heat-check next time I have them both on charge.
[HD2 Accessories] htchd2sucks:
Oh my god they killed...erm

By the way, are you sure that Xperia 1 is...HTC!!!???

Last time I heard it was Sony-Erickson...:o
[HD2 Accessories] ET:
But made by HTC...;)
[HD2 Accessories] htchd2sucks:
oh right...

:o

:confused: my phone manufacturer's hierarchy is all confused now...

:D

Anyway, ok then HTC sucks :D
[HD2 Accessories] reborn_hi:
Just wondering if you just leave your charger on even when it isnt charging?

I am just using my onyx charger to charge my htc and now this i doubt i would use htc charger to charge my phone .
[HD2 Accessories] davidgiga:
Normaly I remove it if I don't use it ;)

Saves energy and fire... normaly:D
[HD2 Accessories] Euroman28:
That sucks... Since HD2 has standard mini USB connector. I use either the charger from "late" Xperia X1 or my Samsung Omnia HD. No problem there :)
[HD2 Accessories] spike15_mk:
Yep my charger is hot

I did not notice before this thread, but yesterday I charged my HD2, and I touch the charger, and it was peaty hot. I do not like this...:confused:
[HD2 Accessories] davidgiga:
I don't understand why they changed the charger cause my old charger from the touch diamond is not even a little bit hot. Maybe it's cheaper for HTC :confused:
[HD2 Accessories] spike15_mk:
Maybe they thought that this charger would be better. But in real world everything is not perfect...Unfortunately :confused:
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] evolutionqy7:
quite disappointingly windows phone doesnt want to let you change sms...recently flashed Chukys rom and the dev had the sms tone changed...

was wondering was there an app/way to change sms ringtone without much bother?

Thanks
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] yoboy:
i am not sure if this is what you're looking for, but if you want to change SMS ringtone in HD2, go to settings -> Sound & Display -> Notification Sounds -> New Message and there you go. Hope this helps.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] otacon:
You could always navigate to Notification Settings to change your sms ringtone.

If you want a custom ringtone, place the mp3 file in 'My Ringtones' folder in your DEVICE memory, and you can select it from the same settings as above.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Kalavere:
You can also put them in My Device/Application Data/Sounds. When you go to Sounds & Notifications they will be in the drop down menu along with the other hundred sounds I routinely delete with every ROM flash, lol. :)
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] evolutionqy7:
hmm you forgot to notice that you have to long press on sms :)

lol ive been messing around with it for so long and never thought to long press on it :)

Thanks to replies

EDIT: Lol theres a severe fault in the system it runs upon...u press on the phone u read the message and the phone still rings...lol bit of a fail there
[EVO 4G Themes and Apps] Minjin:
I thought I'd put up a thread for people to post applications that you might not want to update. Many of us just blindly apply updates on cruise control every time we see them but sometimes that isn't the best course of action. This is for applications that add ads, take away features (in order to put them in pay versions), or decrease reliability. If anyone is aware of a site or better collection of info, please let me know and I will link to it. If you disagree with me (or someone else), post up as well.

- ASTRO File Manager v2.5.2 - adds ads, old version nags to update
[EVO 4G Themes and Apps] Rydah:
unless you google for the pro apl. =]

j/k
[EVO 4G Themes and Apps] kperry1911:
Astro v2.5.1 may be set to expire if I recall. Either way I bought the Pro when it became available @ $3. I don't mind paying for someone's work, especially for a product I find far above other's in it's category that I've used.

-kp
[EVO 4G Themes and Apps] Rydah:
true that. im gonna download an official version since its worth it.
[EVO 4G Themes and Apps] SteelH:
Root explorer is better IMO.
[EVO 4G Themes and Apps] initial:
Shazam 1.3 -> 2.0

Version 2.0 now requires a subscription to lift the 5tags/month limit.
[EVO 4G Themes and Apps] OgremustCrush:
Listen 1.1.3 introduces ask sorts of weird bugs especially with bluetooth headsets. Sticking on 1.1.2 for now.

Posted by my rooted EVO 4G
[EVO 4G Themes and Apps] jeffy2walgreens:
Does anyone have the 1.3 version of Shazam? I flashed my phone to Fresh and I forgot to back it up.
[EVO 4G Themes and Apps] piry525:
If you updated shazam you still get unlimited tagging
[EVO 4G Themes and Apps] ricoo25:
Really? Thanks, was not updating because I was positive that was what the change was.

Anyone else confirm this?
[EVO 4G Themes and Apps] erickjr_88:
I can also confirm this. . . updated version=unlimited tagging
[EVO 4G Themes and Apps] herbthehammer:
not 1.3 but these are old versions

It's alls I gots....

Better than nuthin I suppose

I'm getting more old stuff. I will post different versions when I get them and if I remember to.

demonoid is your friend
[EVO 4G Themes and Apps] herbthehammer:
I'm looking for the hit the penguin game from MTM HZSTUDIO version 1.0 or 1.0.1. The dev started changing the looks and sounds of the game. People loved it and were begging him to revert back to old version that they loved. Dev kept changing the game, gameplay, graphics, and sounds anyways.

I should make myself archive apps and label them BEFORE updating! More times than not, I found that I should have not updated because of one reason or another. At first I thought it was stupid to keep old versions, but now I see why that can be a good thing.
[EVO 4G Themes and Apps] initial:
here's 1.3
[EVO 4G Themes and Apps] Riptide9:
Quote From the Shazam Blog....

"We’ve dedicated this blog post to help resolve any misunderstanding around the continutation of free unlimited tagging for our original users who downloaded Shazam on Android Market before 13th July 2010.

To give you some background, our original Shazam on Android app (version 1) was a great success, quickly becoming one of the most popular downloads on Android Market. In gratitude to our version 1 users who supported us, we decided to adopt a ‘grandfathering’ approach, giving them the best of both worlds – the continuation of unlimited tagging, together with all the great features in our new release (version 2.0). This offer is for the life of their current device.

So how does it work?

Shazam has two consumer offerings:

Shazam: A free to download app supported by advertising, with core functionality and ability to identify up to 5 songs per month

Shazam Encore: A premium version of the app with no advertising, unlimited tagging and additional features.

If you downloaded the free version of Shazam prior to the 13th of July 2010 and tagged at least one song, you can update to the latest version of Shazam and still receive unlimited tagging.

Shazam is supported by advertising, so our existing version 1 users who downloaded 2.0 will still see adverts on their device but still keep unlimited tagging. Grandfathered users can of course purchase Shazam Encore to enjoy the Shazam experience without advertising.

Users who downloaded version 1 and tagged at least one song, but subsequently removed/uninstalled the application also keep unlimited tagging when they download the latest version – you do not have to keep the old version on your phone for unlimited tagging to remain. Users can also uninstall and reinstall 2.0 without affecting their grandfathered- status.

We hope this post has helped clarify things. If you’d like find out more about our Android app, please visit our website and check out the FAQ page."
[EVO 4G Themes and Apps] Minjin:
Most recent Qik update breaks Sense. I'm surprised no one has posted about this before. Roll Qik back by Uninstalling Update in Applications to get rid of the problem.

It shows up as the phone not remembering what to do when you press the home button. It will ask you what launcher to use every time you do a long press regardless if you check the remember box.
[EVO 4G Themes and Apps] SilentSummer:
You don't wanna update Google Voice if you have the number picked for unlimited calling.
[EVO 4G Themes and Apps] dglowe343:
I couldn't live without Root Explorer.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] huzaifarif:
Hey anyone out there please help me since the day i bought my new TMOUS HD2 its getting stuck again and again and specially when i use bluetooth headset for attending calls and the only way to get it back is to take out the battery and reboot.:(

the problem is prevailing no matter what.:mad:

I have HARD RESET my device

I Flashed and tried different radios

I flashed custom ROMS

and i again flashed my TMOUS stock ROM

:eek:BUT THE PROBLEM DOESN'T SEEM TO GIVE UP AT ALL

my device works fine without conneting to my headset but don know what happens to it as soon as i connect my bluetooth and recieve a single call ALAS!!! ITS DEAD AGAIN

pls guys help me

i have used two headsets

1. Motorolla H7500

2. Nokia-BH103

same result with both of them pls any suggestions :confused:
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Foggy79:
Try with an other BT heatset, to see if your headset causes the issues. If you have the same issue with the other headset, you might think of returning the device for waranty (as I see you already hard reset a few times with the original ROM aswell)

Edit: saw you already used a 2nd headset... hmmm does your BT work normaly when transfering files?
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] huzaifarif:
yes evrything else is extremely well except this just one problem
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Foggy79:
So with a complete clean stockrom installation it doesn't work with 2 different BT headsets?...

Hmmm could be the BT chip thats causing issues when connected true a BT headset?

You might want to send it back for warranty i'm afraid.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] huzaifarif:
I'm thinking on it as well neways thank you :)
[Hero CDMA Q&A, Help & Troubleshooting] buddho81:
I just rooted and installed Darchdroid v2.7 ROM on my phone and I LOVE IT!!!!!

Only issue I have is that my 3g internet is not working!!! how do i get this to work??

All i see is a few bars on top and when I go into surf the net it wont work...Only works on wifi!!!

Please help!!! Thanks in advance!

Cheers!
[Hero CDMA Q&A, Help & Troubleshooting] buddho81:
Any solution???
[Hero CDMA Q&A, Help & Troubleshooting] boydroid:
Turn mobile network off then back on
[Nexus One Q&A, Help & Troubleshooting] sheik124:
The in-call screen + incoming calls show extremely low quality contact pictures. My Touch Pro did better :confused:

Anything we can do?
[G1 Q&A, Help & Troubleshooting] MV10:
I know that ECC refers to the error correction checksum used to detect memory errors... but I find it awfully suspicious that the two supposed ECC errors fall on the very first and last slots on the misc range -- particularly since everybody else with this problem who posts the results of attempts to troubleshoot it or fix it reports exactly the same thing.

In other words, I assume the error message is wrong. This is pretty much the only reason I don't just conclude that the memory is actually hosed and go shopping for a new phone.

Oh, and... bump. :D
[G1 Q&A, Help & Troubleshooting] lbcoder:
You are certainly telling the truth about it being quite long. That fact does, unfortunately, make it somewhat difficult to read.

I assume that you've seen a few of ezterry's and/or my own posts about the partitions, which is probably where you saw the info on the misc partition.

In any case, the misc partition isn't a "filesystem" partition as you are familiar with. It is actually just a simple data structure. In fact, only the system, cache, and userdata partitions are actually filesystem partitions, and the cache partition is only a filesystem partition part of the time -- during radio and spl updates, it also is used as a simple data structure with a header field and a payload field. That, along with the misc partition, instructs the SPL to perform a radio or spl update.

Now there is a possibility that it may be possible to salvage the device without a working misc partition. Specifically, the requirement is that you get yourself a high-engineering SPL (one with the ability to fastboot a radio image -- note: it is FAST boot, not flashboot).

One important thing to note that might make things easier is that an error "finding" the misc partition *might not imply a failed misc partition*. It could possibly be a failed CACHE partition. Have you tried FORMATTING your cache partition?

In any case, you are no doubt really wondering about my statement that you might be able to update the SPL without the use of a misc partition.... Read THIS thread and you will see how the partition tables are defined and how they can be overridden. This suggests a way that you can actually DEFINE the SPL partition to the linux kernel, which in turn, should allow you to flash_image an SPL update. What you need to do is determine the starting offset and length of the SPL partition, and define it along with the rest of the partitions on the kernel command line. Once this is done, you should be able to fastboot flash a radio update to the device.

Note: Having just done an RC29 NBH file, there is PRECISELY ONE high-engineering SPL that you can install to the device safely.... 1.33.2003 (ending with a THREE -- very important, a 5 is a brick when combined with an rc29's radio).

Also note: I don't take any responsibility if you fry it completely trying this idiotic procedure without a jtag standing by. It is quite risky. I suggest it because it may be your best chance of getting through this.

Note: fastboot does NOT require a 2.x radio image. Fastboot requires an engineering SPL, which for the same reason, you can't install.

Now as for the location of the read/write errors.... you think that it is suspicious that they occur at the first and last slot of the memory range...

Well this is not unexpected since there are only two slots. Each of 128 kB. The first at 0 offset wrt the start, the second at 20000 offset wrt the start. The ECC error itself says that each of the two blocks has failed whatever operation it was trying to perform.

I suggest that your first step might be to try again writing the RC29 NBH file.
[G1 Q&A, Help & Troubleshooting] MV10:
Thank you for the explanations and all the details.

I have actually reloaded RC29 quite a few times. I followed the directions from scratch a couple times in case I had gotten something wrong (of course, this was easy to do since I get stuck pretty early in the process).

I'll try formatting CACHE and I'll take a look at using the SPL you reference and report back later.

I really appreciate the assistance.
[G1 Q&A, Help & Troubleshooting] MV10:
Ah, just realized that when you do "Wipe cache" from RA recovery, formatting cache is the second step. Since that is immediately followed by another "Can't read MISC" error message, I guess formatting doesn't fix my misc issue.

In this paragraph:

Your "THIS" didn't link to anything. I'll go search for what you're referring to, since this would appear to be my only remaining solution. No JTAG handy, but if someone of your experience thinks this is probably my last-ditch option, I don't have much to lose anyway, right? I'll take it slowly.

Edit: I think this is it? xdaforums.com/showthread.php?t=704560 Pretty clever... crazy and dangerous, sure, but what the hell, it's just a phone, lol...

Again, thanks for taking the time to help out.
[G1 Q&A, Help & Troubleshooting] ezterry:
Before re-writing partitions find a recovery with 'erase_image' (I hear tell clockwork has it) install and try:

erase_image misc

then

flash_image misc <misc.img>

where misc.img is an old nandroid backup from a phone of the same region as your own (least its preferable its the same region your CID is in the structure)

It may correct the issue... if not we can try to flash an engineering SPL via flash_image..

I feel this is very safe in theory (as we don't have to worry about boot mode 3.. thus if a valid SPL is flashed you won't completely brick).. However we have no safeguards at this point in time so be careful that you really understand what is going on.. else you will write garbage to the SPL, and there is no helping that w/o JTAG.

(btw.. the SPL .. even the full engineering ones like 1.33.2003 and 1.33.2005 wont actually let you erase misc.. but will let you flash it)
[G1 Q&A, Help & Troubleshooting] MV10:
Thank you, I'll try it later today.

Not that it's relevant to getting me fixed, probably, but no idea how/why this problem crops up? Or is it more a case of an error that can have multiple causes? I found it interesting that so many people were reporting it across the various Android forums, and there seemed to be no attempt to explain it. That kind of thing always makes me curious, particularly in an environment like this -- a room full of curious "dig in and figure it out" personalities...
[G1 Q&A, Help & Troubleshooting] lbcoder:
If it ever happened to me, I would certainly try to figure it out, however this is really difficult since it has never happened to me. I don't think that it is anywhere near as common as you think.

What I believe about the situation at the moment is that it is *probably* a failure somewhere else along the line that simply has this SIDE EFFECT.

ezterry: Do you remember which memory address ranges are written by an nbh file? I recall that the nbh file has divisions for the different partitions, so I suspect that it may not write *everything*. Maybe misc and/or cache are not written?

Note: I have seen plenty of instances of the cache partition getting borked and having weird side-effect. The problem with the cache partition and why IT gets into weird states is that it is a dual-purpose partition -- sometimes a yaffs2 filesystem, sometimes a simple data structure, so if it gets into the data structure mode and something tries to use it as a filesystem, you end up with some interesting side-effects.
[G1 Q&A, Help & Troubleshooting] ezterry:
The nbh is just a custom archive the header has 3 arrays of 32bit indicating the following for each partition included

> Partition type (this determines the partition via some mapping to flash radio,hboot,misc,cache,recovery,boot,system,splash1,diag)

> Partition offset from start of the nbh file (signature removed if included)

> size of image

The diagnostic nbh only has the fake 'diag' image.. however most others in the wild seem to have radio, hboot, splash1, recovery, system, cache, userdata...

I don't think I've seen one with misc.

Certainly none of my current collection have it. I Wonder if they allow it?
[G1 Q&A, Help & Troubleshooting] MV10:
Clockwork's "erase_image misc" returns an error:

mtd: erase failure at 0x00000000

I also tried wiping and formatting the cache again, on the off chance that maybe clockwork did something differently. Nothing new to report there.

As for this kernel partition approach, do I correctly understand that I would be telling the kernel to create a new partition name mapped to a range which precedes misc where the SPL is located? I assume I can derive the size from an img of the stock SPL of the same version. Any tips on how I can figure out where it starts? (Apologies if it's in that thread Ibcoder referenced, I haven't finished reading it yet.)

Or am I thinking about this completely wrong?
[G1 Q&A, Help & Troubleshooting] ezterry:
Search for my post with the kernel command line with hboot replacing userdata.. it deliberately is not step by step but has the info needed.
[G1 Q&A, Help & Troubleshooting] MV10:
On a somewhat peripherally-related note, I see in this post in the De-bricking thread:

xdaforums.com/showpost.php?p=7072492&postcount=195

Ibcoder writes: 3) This person goes to boot to the recovery by issuing a "reboot recovery", which sets the command field of the MISC partition to boot-recovery and reboots.

Earlier I had thought about asking whether "reboot recovery" writes to MISC, since I issued that command from the RA console yesterday and to my surprise it worked. I figured I must have misunderstood something and maybe reboot recovery used some mechanism other than writing to MISC, but now I've run across the comment above.

Wouldn't that boot mode flag be the same thing recovery should use to finish installing a radio image?

ezterry, is this the post you're referring to?

xdaforums.com/showpost.php?p=7064255&postcount=187
[G1 Q&A, Help & Troubleshooting] lbcoder:
Suggesting, of course, that the misc partition itself is actually quite fine, but whatever subsystems responsible for screwing up when it screws up for you are in some other way broken.... which is not inconsistent with the theories I have presented above. Specifically, I am still quite concerned about your cache partition being somehow defective since it is known for having weird side-effects.

What you may possibly be able to do is hack the reboot command into "reboot flash-hboot"... be ***absolutely certain*** that you get your cache partition set up correctly and fully verified before you do this though, otherwise you WILL need jtag to fix it.
[G1 Q&A, Help & Troubleshooting] MV10:
Later I wondered whether reboot had options to specify the flashing modes. I take it from your response that it does not. Given my meager relevant knowledge, significant hand-holding would probably be required to pull that one off!
[G1 Q&A, Help & Troubleshooting] MV10:
Another oddity I have noticed: my own G1 shows a device ID of HT91CGZ02056 (through something like "adb devices" for example)... but my wife's G1 (with the MISC issue, or whatever it is) just returns a string of zeros: 000000000000. First noticed that in the nandroid backup directory name.

Not sure if that tells anyone anything useful or interesting, but it sure seems weird.
[G1 Q&A, Help & Troubleshooting] lbcoder:
It could mean that there is a serious defect.... or it could be the same glitch that is causing you problems with misc. Remember that the device ID is stored within the same chip as the misc partition, just at a non-writeable address.
[G1 Q&A, Help & Troubleshooting] MV10:
Ha, interesting, I didn't know there was any sort of relationship there. Very interesting.

Well, at this point my wife is freaking out without a phone :D so I'm just buying her a Galaxy S (yeah I know, Samsung... but frickin' T-Mo doesn't have anything else particularly compelling).

I'm sort of interested in what's wrong with her G1 and I have an unhealthy urge to keep fiddling with it, but honestly I can't justify spending much more time on it right now, too many other things going on in my non-phone-based life.

That means I have a thoroughly unexciting RC29 G1. I assume OTA updates aren't likely to work either (assuming they're still sent out). If either you or ezterry would have any interest in this device (maybe some questions about what went wrong since you haven't seen a MISC failure?), shoot me a PM, I'll see about shipping it off to one of you.

Regardless, I can't express how much I appreciate both of your attempts to help a complete stranger, and I look forward to reading about all the other weird and interesting stuff you guys dig up in the future...