Database Develop

(Untethered, official) Kaiser not booting in? HR doesn't help.

Has anyone ever encountered the Kaiser's becoming completely dead, out of a sudden? HR doesn't help. It has the official Kaiser ROM - and not even any hacks.
After starting, it just prints "smart mobility", vibrates once and, atter a while, repeats this in an infinite loop.

Menneisyys,
my unit did exactly the same thing. Had to send it back, unit was exchanged for a new one.
This behavior goes hand in hand wit the "Standby of Death" and "Red Light of Death" behavior where the unit will no longer wake up from standby or will no longer start up even though a charger is connected. There is a thread on XDA-dev. about this syndrom.
The only information that I can give you is that my first Kaiser which finally died exactly like yours mid-December showed erratic behavior like restarting three times after soft reset and the SoD right from coming out of the box. The replacement unit never showed anything similar.
As far as I can remember there is a good chance that HTC as released a faulty production lot to the market showing these problems.
Get your unit replaced under warranty. Re-flash or any other repair attempts won't work.
Rgds
Joe

I had that issue. I went into bootloader and flashed a new ROM and it fixed the problem.

I am having the same problem now too - I can get it to hard reset after some twists, but it refuses to work when I restore a backup, I'll see if I can get a case that I can repeat so I can send it back...

TF3D Display issue

Hi all,
This morning my phone was still doing fine, alarm went off, display was normal. When I unplugged it from the charger to go to work, the display turned into the attached screenshot. Funny thing is it wasn't hanging, the numbers on the clock was still flipping over
Has anyone seen this before, but more importantly, is there a fix for it?
Thanks

I had that. Only thing is to re-insert the battery.

lude219 said:
I had that. Only thing is to re-insert the battery.
Click to expand...
Click to collapse
I did a soft reset, which fixed it. Just a bit concerned as yesterday early morning, while charging, the phone hanged.
Maybe time for a new ROM

Thats if its a software issue and not a hardware issue. I've posted on this problem I have and its similar to yours.
Its related to the 3d driver from htc. either its the poorly written api or the poor 3d chip is the culprit.
Disable TF3d and you will not see this happening again. But then, it wouldnt be a diamond without Manila, would it?

Might be a good opportunity to "upgrade" your ROM....

alright after almost 1 week of testing, I can finally conclude that this problem has disappeared.
I've tried changing to v1.93 Olinex and tested the roms from SwiftBL, Panosha, Vic etc. None was able to resolve the problem until I tried Dutty's v2.6. The problem no long appears and has been rock stable, be it overnight or normal usage.
A closer look revealed that Dutty's rom has a newer version of Manila, while Swift and Vic (not sure about Panosha)'s romes had an older version.
Give it a try guys and see if it works for you.

Dimaond Gets Hot and Screen Alignment Goes Out

I have done a reasonable amount of searching on this and have not found anything specific to my problem so figured I should post a question.
I have an issue with my Dimaond when it gets hot generally either using Wifi or Phone Data connection that the screen goes out. Basically everything goes to the left side of the phone so if you hit the Task Icon in the top right corner you get the Start Menu. Phone is basically useless at this point and you have to wait for it to cool down. Has happened since day one and is generally worse when using it when charging. I was watching Utube on it the other night 5min video while on AC charge and it went out. I am running Dutty 2.5 Rom and 25.07 radio have tryed 25.08 and 25.05 no difference was happening when the phone had orginal HTC ROM as well. Also will happen on a long call if the screen is on.
Basically feel issue is hardware related and maybe faulty screen still under warrenty so wanted to know peoples opinion on weather I should send back. Problem is will take a couple of weeks and I don't really wnat to wait that long if I can help it. Also assume it would be best to flash standard ROM back, should I do anything with HARDSPL eg should this be changed back as well if I send it back.
And before anyone says it I have tryed searching this topic and have found lots about HOT dimaonds but nothing related to screen going out at the same time :-(
Thanks

I had this issue in my JasJam (Hermes) whre the screen would simply go white after a while of use and I would have to leave it for a while for it to work again.
Unfortunately it sa hardware issue and you should claim a warranty repair on it

I can't see how this could be a software problem so I figured it must be the screen eg hardware related. Would be nice to know if anyone has had the same issue with a dimaond... Seems we may be spending some time apart, just hope it doesn't take long to fix..

I've had the same issue
http://forum.xda-developers.com/showthread.php?t=428976
My first device had been replaced recently (i.e. today) by my network provider (o2) and the new device seems to work without any problems now even if it's "hot".
(i.e. default screen adjustment + creating heat by activating the phone, wlan, bt + recharging it)

I sent an email to HTC regarding the fault and they said it would have to go back for a warrenty repair. I brought it through a resellar so has to go back to HK from NZ so will be away three weeks uurggghhh... Just seems odd I don't have any physical damage on the screen but hte problem has been around since day one as I remember having the problem the first day I got it. Juyst seems to be getting worse and is easily reproduced by usiung utube over wifi gets hot and it is all over. Just wondering if I should put an offical ROM from HTC back on the device before I send it back as I currenty am running Dutty ROM, what do you think....

i put the original rom back on and they still found out the the rom had been flashed, and would not repair on warranty

yep, i also asked about this problem
http://forum.xda-developers.com/showthread.php?t=438733
there are some youtube video's of how the phone behaves
my phone seems to do it less frequently since stopping using panosha's rom
im using alpha zero 7 at the moment..
i've also noticed that it isnt necessarily a heat issue, my phone does it completely at random
yesterday i found though, that when the phone did the alignment issue, i gave it a good shake.. and hey.. its all aligned again?!
maybe it was just a fluke, it hasnt freaked out since..
holding thumbs

Hey,
I also have the same screen problem, but my Alignment goes to right.
If I press on the left side, a press on the right side is recognized.
Good to know that Im not the only one with this problem.
greets doena

I got my phone back a week ago replaced the screen has been away for over two months, complete disaster, anyway all sorted now and I have not had the problem since....

I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.

Minus-1 said:
I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.
Click to expand...
Click to collapse
Hardware's fault ? Most likely not. I will give u an example of why I think it was software related. My device ran hot as well but I simply switched roms and now it's the complete opposite. Your most recent device most likely come with a different Rom in the phone.

Diamond: some production series better than others?

I just got my Diamond back from repairs and wanted to compare experiences:
1)
I first bought a Diamond two months ago. It came with 1.37 ROM series on it, the screen wasn't too yellowish, but touch function wasn't responsive and the GPS was a MESS!
(of course, I tried many ROMs official and unofficial, almost every Radio ROM and various Hard-SPL. None of that fixed the problems.)
I could cope with with the other flaws, but I just couldn't bear my GPS wasn't getting a fix, no matter how much sattelits were in view...
It worked at first, but soon started to display '66666' instead of the location and finally, it would never display any location again.
I tried every tips and tricks and softs, it helped giving me more and more satellits in view and apparently active, but at the end my crappy GPS could never turn the datas received into a proper location...
2)
I sent my device back to warranty (after flashing back to official ROM and SPL) and had to wait for about a month.
(the technician at first tought I was just a noob unable to set his phone properly, but after two days of attempts, he had to admit that there was something wrong with my phone and sent it to the the headquarter for replacement of motherboard and so on.
3)
The new phone I got came directly with 1.93 ROM and a little bit more yellowish screen, though, there is no spot or stain on it. So the coulour doesnt bother me.
But from the beginning I noticed the new phone was much more responsive even at the slightest touch.
From the first try, the GPS got a fix in about 1 mn time, with only 3-4 satelits in view.
I installed Hard-SPL and the latest Australian Official ROM, and though the screen seems now a little less responsive than before, the GPS is still working, fine.
I'm a VERY happy user of Diamond now, but I'm still wondering one thing:
it looks like once the warranty technicians understood that I was very demanding about quality and complete functions, they took time but gave me a phone totally different in terms of behaviour and quality of the components sensitivity of screen, GPS etc.
Is there some bad production series that they never tells publicly about, and much more better series that they give you as a replacement once they understand you will bother them until the end of time if you are not satsified?
Plz tell your experience about having received two new diamonds with totally different behaviour and quality of the components.

I guess you are totally right!!!
My first device was pealing paint in the aluminium frame on the second day, work very good by the way.
Now i´m on the second device and i my hardware keys, especially the call button is sometimes irresponsive and i have to push it several times to enter the dial.
Tried cooked rooms as well, and the call button issue still remains, so i´m a little unhappy with my diamond experience.

I've noticed that whenever i turn on my display after having left the diamond unused for sometime the lcd doesn't switch on smoothly, what i mean is that it first displays a grey pattern(only for a ms or so) and then the desktop( lcd off>>grey flash>>desktop). Usually the transition from off to desktop is quite smooth, but in my case its not!
Is this a s/w issue or h/w ?

I've never experienced that particular problem myself, but sounds like H/W problem to me...

just been through a couple of other threads related to the grey screen of death...i've had it once...it happened while i ended a call, had to soft reset to resolve it.
take a look at the grey screen of death i'm talking about

Pretty scary indeed!
It might not be a coincidence that you experienced both: grey transition when switching on the screen and once, the grey screen of death after a call...
Two different effects of the same defective part in your H/W?

a solution!, almost
untill now i've had auto brightness control switched off and the brightness was set to minimum to save battery life, but now i just tried switching on auto adjust backlight and the problem seems to have vanished.....coming out of standby is smooth as ever!
although i've to say that i don't quite understand the logic behind it.
*EDIT*
it doesn't help for long

blufade said:
a solution!, almost
*EDIT*
it doesn't help for long
Click to expand...
Click to collapse
This is what I was worrying about...
Your method sounded like a work around to avoid the display failure. But as a matter of fact, there must be a reason for the display to fail. (bad screen, power supply or something...)
By the way, I'm more and more convinced about my assumption that there are bad production series and better ones:
Today I had my device connected to my PC through USB for a couple of hours. In the meantime, I was downloading and deleting messages, watching google video on opera, after that I used wifi etc.
In this situation, my first Diamond would have got hot like hell and my hand could barely stand the pain...
Since many people were complaining about over-heat problems, I thought that was a common problem with Diamond.
But the new one did not get that hot. Just a little over-warmed, but definitely not too hot. From that phenomenon, I can see what I felt about a better touch-flow behaviour, a better GPS and so on is a part of a whole:
I was first sold a ****ty phone, and now I finally got a proper Diamond!
People with bad series, you don't have to cope with all those troubles, ask for a replacement phone!

my diamond gets heated up quite a bit at times....but i dont fully uderstand what exactly is the cause.....i've had experiences with the diamond getting pretty hot while using wifi & or gps and on another occasion i was watching a DVDRIP via wifi(@ full power) using core player and also with gps cycle running in the backgroud, still the diamond stayed well within reasonable limits.
i think it has to be a software problem, possibly the radio s/w
would you mind sharing the radio version of your diamond?

As written in my signature, I'm using the 1.00.25 which is included in all latest official ROMs.
By the way, I hope you did not cast a spell on me! (just kidding)
Today I experienced my first grey screen!!!
My Diamond was connected to the PC through USB cable, downloading e-mails, and I got a phone call. When I hung the phone, It suddainly happened, for the first time in my Diamond user carreer!
Just for one second, looking like an old black and white TV screen trying to tune on channels.
Hope that was the first and last time. In ordinary calls, (without being synchronized to the PC at the same time, it never happened so far...

sorry to hear that my friend
My Diamond was connected to the PC through USB cable, downloading e-mails, and I got a phone call. When I hung the phone, It suddainly happened, for the first time in my Diamond user carreer!
Click to expand...
Click to collapse
I'd the same experience except for the fact that my diamond wasn't connected to a PC.
I hard reseted my diamond yesterday, but the grey splash while i turn on the display from standby(post 3) still exists ( ......i don't suppose its a software problem anymore.

blufade said:
i don't suppose its a software problem anymore.
Click to expand...
Click to collapse
Why not trying to send it back to the seller and get a new one?
This problem is easy to demonstrate to the technicians, and I don't think they will be cheeky enough to say that's a normal phenomenon!

This problem is easy to demonstrate to the technicians, and I don't think they will be cheeky enough to say that's a normal phenomenon!
Click to expand...
Click to collapse
not that easy.....the thing is that if we turn on & off the lcd without a gap of atleast 4-5 min(dono exactly) i dont see that grey splash
i think im going to wait another 3-4 months before i approach for warranty.

I had that "gray splash" problem with my Kaiser and Diamond.
Hard reset also didn't work like above. For both devices the fix was simply flashing to a different (cooked) ROM.

As mentioned in another thread, the grey screen problem was fixed (as least for me when I flashed to dutty's rom)

blufade said:
not that easy.....the thing is that if we turn on & off the lcd without a gap of atleast 4-5 min(dono exactly) i dont see that grey splash
i think im going to wait another 3-4 months before i approach for warranty.
Click to expand...
Click to collapse
You can stay there and wait for 5 more minutes in the shop while they are attending other customers, just to proove your point.
If they are honest, they will not deny the fact!
foxium said:
I had that "gray splash" problem with my Kaiser and Diamond.
Hard reset also didn't work like above. For both devices the fix was simply flashing to a different (cooked) ROM.
Click to expand...
Click to collapse
knave said:
As mentioned in another thread, the grey screen problem was fixed (as least for me when I flashed to dutty's rom)
Click to expand...
Click to collapse
There might be some tweaks in the cooked ROMs that avoid the problem, or it might be due to some bad flashing or defective hardware.
If not, how do you explain that I've never experienced this with my previous HTC phones (wizard, Trinity...) nor I experienced it with my Diamonds (the first one and the new one) with stock or cooked ROMs.
except for that very special time, when I received a call while downloading messages through Active Sync.

Touch Screen has stopped working

Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.

Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.

Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.

When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.

Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks

gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night

Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.

Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.