Database Develop

[help] Diamond only powers on sometimes!

Hello guys!
I'm having some trouble with my HTC Touch Diamond. I am running the latest ROM, and the phone has worked perfectly since I've got it!
But one day it suddenly powered itself of during a phonecall and I was not able to power it on again. I removed the battery, put it in again, didn't work. Took out the battery and waited for almost 30 minutes, tried again and now it worked!
Since then the phone locks up in no systematical pattern (when I wake up in the morning it mybe locked itself, sometimes when I listen to the radio or typing an SMS..). Do you have any idea what the problem might be? Can't type in the serial number as I just have managed to turn it on.
What should be mentioned is the behavior when trying to start it. Either the phone gives no respons, or it "buzzez" and the display shows "touch diamond", but the rom version is not appearing down to the right. When it starts, it starts just as it should and no error messages is displayed.
I have not tried doing a hard reset yet, which I must say is considered the last option.
Have anyone experienced something like this? Or does anyone have a suggestion about what might be causing this?
Thanks on beforehand
Edit: have performed a hard reset now (did not format the 4gb). But the problem is not gone.. The phone just died while surfing. Now it locks at the green windows mobile-screen just before the homescreen loads (if it even boots at all...)
Please help anyone!

Ridiculously easy to corrupt settings - Normal?

I was just getting over the initial buyers remorse phase for my galaxy (or in my case, flashers remorse, even though I run stock JPY and it's fine, I have this urge to re-exchange it for a SLOWER stock Vodaphone Australia 2.2 version that's probably more buggy, but at least truly stock), when I drained my battery to 1% to test battery life, and shut it off manually.
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) left right and center then went straight back into default first-boot menu, like the very day I received the phone, or after a hard reset. The funny thing was, instead of having default values selected, it had the ones I had already put in. I thought it would be fine after that. Wrong.
I tried rebooting it again to see if it fixed itself, and it does the same with the forced closes. I uninstall my background and re-install it, and save some settings. When it boots it restores the live background back to it's stock settings (the live wallpaper I chose is still there, but the settings for it are not).
At this point I'm scratching my head so I uninstall all apps. This time on boot it doesn't throw up "force close" errors, but instead force-closes a single app or service for me on boot, with the one buzz, then three quick buzzes. Sigh... I have to factory reset my phone. One thing that particularly annoyed me was the fact I moved all my apps (AngryBirds ) to my external SD card, yet miraculously, after the reset my phone doesn't seem to think it's there anymore! Another thing I'm pondering is that if I didn't reset my phone like this, would this still have occurred?
Runs perfectly fine after the factory reset, with no errors or anything on boot as of yet. I have been compulsively rebooting it ever since just to find out, LOL!
Is this a 'normal' sort of thing to happen on the SGS, or is just through shear coincidence the combination of me restarting the phone in it's booting phase + the low battery life screwed up some boot settings while the phone was writing to it, or is it some hardware error? I can see this as particularly annoying if it were to happen every month or so. Coming from an old brick phone with something like 8000 messages on it, it'd be inconvenient to say the least to start deleting everything periodically... I guess I can use apps to back-up data when this occurs, but some apps don't even work after it's been erroring out on me. *Pulls hair out*
TL;DR:
Reset my phone while it was booting (still on the GT-I9000 screen) on a low (1%) battery and it broke my phone settings. Forced closes unknown app/service on boot with no 3rd party apps installed, but still boots to home. Force closes 3rd party apps frequently if they're installed. Factory Reset/Wipe. Problem Solved. Annoyed. RAGE.

next time something like this happens use adb logcat to figure out what is actually going wrong

exclamationmark said:
...
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) ...
Click to expand...
Click to collapse
you are not alone . after draining battery , starting it accidently up (drained) in middle of booting , killed it for me, well not killed but wouldnt boot for me and I had to the the factory reset. oh and since the nice bzz ... bzz bzz bzz I hear more often I would like to ( here was I ignored crying about it http://forum.xda-developers.com/showthread.php?t=937938 )

Yeah I'll definitely boot up logcat if it happens again. I'm just hoping this isn't a regular occurrence . As long as I don't do anything stupid like this again, I'm thinking it should be fine.
The third time this happens, it's going back to the service center, so it's got two chances left! Another thing I failed to mention was that it was chewing up like 200mb~ ram with level 1+2 ram cleared, without loading back into the homescreen, before the factory reset. Probably the stupid forced close app/service leaking >.>
Pagot, if that were me and continual factory resets were the only way to fix it (or didn't fix it) I'd flash it back to stock (or just remove root) and return it to the service center if that's an option. Sounds like something got corrupted or didn't get flashed properly. Either way I'd let THEM waste their time sorting it out because no amount of flashing is going to solve a hardware issue if it turns out to be one.

exclamationmark:
(had stock, so just root removing) but I know how our service centers work (and I would have to bring it even to our carrier) they wouldnt even talk to me if I didnt do the factory reset and the first thing they would do "reflash and factory reset"
right now I am not playing on the phone so much anymore. no lust or time so no idae if my apps are still fcing so often . And I installed speedmod and made a backup so I can revert back if something happens. So will see.
Wanted to just write about the battery down +(or) not full boot = corruption

[Q] Serious nexus one problem

Hi all
I got a serious problem, my nexus one is some times behaving weird, it randomly reboots, vibrates makes some weird multi-vibrations or gets stuck vibrating, the phone is extremely slow, so slow that all animations are like a photo show, the boot process and animation is the same, it is using about 3-4 minutes to boot, on top of that the internal clock is getting completely out of sync with some hours!
In this mode the phone is unreliable and unusable, but some times it will work again, smooth/fast animations as always, what am I doing wrong, I can not understand it and I have tried to search the Internet for solutions for two days now without any luck!
I got cyanogenmod 7.1 installed, and have tried stock android and got exactly the same problem, I have wyped dalvik cache and performed a complete factory reset nothing helps, but then suddenly it works again without any problems for some hours, now it got the same problems again!
I had no luck observing any specific pattern where it will fail, so I am kind of lost on this one!
I hope someone can help.
With best regards
ZigZaggh

Bad news. Multiple (7) vibrations mean - your phone's CPU is overheating. Nothing to do about it, it's dead.

Chances of HTC fixing it are about 0, especially if the bootloader is unlocked.

Thanks for the answers, sure that is the problem? Now it has been working for some days, with no problems at all, if it is a hardware failure, should the problem not stay ore occur at hi work loads?
Yeah HTC will probably not tush it, dam it was a nice phone

[Q] Phone freezes and repeats vibration pattern

Hi. My Galaxy S recently became unresponsive. I plan to root it and then flash a ROM, hopefully to fix this issue and upgrade it. The problem is that a few seconds after booting it becomes unresponsive and goes through a cycle repeating vibrations: one short vibration followed by a pause then three consecutive short vibrations, then a pause, and does so until it drains the battery. All the while the phone is unusable in anyway. This is an AT&T phone with no changes since purchase. Any advice on how to proceed? Thank you all in advance.

binnaeus said:
Hi. My Galaxy S recently became unresponsive. I plan to root it and then flash a ROM, hopefully to fix this issue and upgrade it. The problem is that a few seconds after booting it becomes unresponsive and goes through a cycle repeating vibrations: one short vibration followed by a pause then three consecutive short vibrations, then a pause, and does so until it drains the battery. All the while the phone is unusable in anyway. This is an AT&T phone with no changes since purchase. Any advice on how to proceed? Thank you all in advance.
Click to expand...
Click to collapse
Are you using a external sd card? If so, try booting without it.
If it's not the case, are you able to connect your phone to your pc? Backup your stuff? From there, you could boot in recovery and factory reset (this will wipe your device).
In any case, backing up your stuff would be priority atm.

BWolf56 said:
Are you using a external sd card? If so, try booting without it.
If it's not the case, are you able to connect your phone to your pc? Backup your stuff? From there, you could boot in recovery and factory reset (this will wipe your device).
In any case, backing up your stuff would be priority atm.
Click to expand...
Click to collapse
Thank you BWolf56 for the reply. No external SD. Will be attempting the recovery. I'm wondering if the vibration pattern is some kind of an error message that can be interpreted.

binnaeus said:
Thank you BWolf56 for the reply. No external SD. Will be attempting the recovery. I'm wondering if the vibration pattern is some kind of an error message that can be interpreted.
Click to expand...
Click to collapse
If you're on a stock, it's usually something that got corrupted so a wipe/factory reset can fix it. The vibration is most likely the phone letting you know if turning off (ever noticed that when you're turning it off, it vibrates to "confirm").

BWolf56 said:
If you're on a stock, it's usually something that got corrupted so a wipe/factory reset can fix it. The vibration is most likely the phone letting you know if turning off (ever noticed that when you're turning it off, it vibrates to "confirm").
Click to expand...
Click to collapse
Thanks for the follow up, it seems to have worked, although the vibrations are different from those you get right after the phone starts up, the ones I experienced were continuous and drained up the battery every time.

phone turns off by itself

Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?

terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial

Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.

terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on

Nope it's off

Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.

I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?

terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.

The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater