Database Develop

HTC Diamond shuts down if there is no network - any help?

This is my las try, I posted this message twice in the XDA forum.
I guess if no one having this issue I'll not bother folks with this again and will try to leave with it...
The problem goes like this, when I'm out of cellular reception area the phone shuts down and the only way to turn it back up is to remove and put back the battery.
I suspect this is some sort of strange power saving setting gone wrong.
Any idea on what can I do about it? Registry settings or something?
ROM: 1.93.831.1

Well, without knowing any better I've have to guess it was a problem with the Radio ROM. Are you using .08 or .11 radio version? If so, I'd try 0.5 - it seems to be the most stable for the majority of people here. I had heaps of problems (random freezes/crashes) when using 0.8 or 0.11 that forced me into a battery removal fix quite a few times...
If you've upgraded your Radio ROM (by itself) then most people suggest doing a hard reset afterwards, even though you don't *have* to, so make sure you try that...

obender said:
This is my las try, I posted this message twice in the XDA forum.
I guess if no one having this issue I'll not bother folks with this again and will try to leave with it...
The problem goes like this, when I'm out of cellular reception area the phone shuts down and the only way to turn it back up is to remove and put back the battery.
I suspect this is some sort of strange power saving setting gone wrong.
Any idea on what can I do about it? Registry settings or something?
ROM: 1.93.831.1
Click to expand...
Click to collapse
It happes to my diamond too. Now i've got the lastest rom with latest radio (05) and in a week it happened only one time (before it happens a lot of time during a single day..)..
I've buy a new battery today just to be sure that it not a battery problem. I'll let you know in the next days.
By the way in my case i've see that the phone does not shut down when goes out of signal, but before shutting down i hear a short sound than the signal is missed and then the phone shutdown. Many times i need to wait a lot of minutes to power on the diamond. I've also try to froze the battery in this cases and like a kind of magic it's possibile to power on immediatly the baby. (this is why i've bought a new battery...)

I do also experience this problem, after upgraded my ROM to 1.93.831.1, when I'm out of cellular reception area the phone shuts down by itself.
I bought it to HTC service centre, they say no problem was found but they reload the Rom and replaced a new battery.
The problem still persist when i enter a no Network area, the phone automatically shut down again ...
Any idea on what can I do about it?
Please advise .....

Ummhh. Having the same problem here! Read a PDA Magazine and it says all bugs from Diamond have been removed and thats why Diamond 2 is released!

***BUMP***
Need a fix quick please!
@mod: please can you sticky this for a few day?

found the problem... sent it off two tmobile and they just took the handset not the battery...
they said they found no problem and made no changes.... i received the phone after 1 month and i put the battery in and it worked fine... used it with my car charger and started again so i left the battery out of the phone for 2 days then tried and works fine now.....

airplane mode reboots?

I know I read people discussing this in the past - but was unsure if a solution was ever reached? I'm running Myn's latest Donut and am still getting airplane mode reboots.
Thanks

same here
berardi said:
I know I read people discussing this in the past - but was unsure if a solution was ever reached? I'm running Myn's latest Donut and am still getting airplane mode reboots.
Thanks
Click to expand...
Click to collapse
me too, i am running "Incubus26Jc's Super Eclair Lite 2.1 [RLS5] - [5/8/10]" and always got airplane mode reboots.

Me too!!!
Typically right before we take off just after they tell everyone to shut off their portable electronics and phones.

Just put my phone in Airplane mode. No reboot. Running RLS5 of myn's warm donut.
Is there a step I am missing here?

crobs808 said:
Just put my phone in Airplane mode. No reboot. Running RLS5 of myn's warm donut.
Is there a step I am missing here?
Click to expand...
Click to collapse
It doesn't always happen instantly usually takes a while.

berardi said:
It doesn't always happen instantly usually takes a while.
Click to expand...
Click to collapse
I have been using RLS5 for quite some time now and put my phone in Airplane Mode every day for work(7 hours+). When I leave, I turn it off. No issues here.

Mine will reboot when in airplane mode for unknown amount of time (usually after going to sleep) OR will freeze (screen off) after losing all radio signals for a while.

Jiggity Janx said:
I have been using RLS5 for quite some time now and put my phone in Airplane Mode every day for work(7 hours+). When I leave, I turn it off. No issues here.
Click to expand...
Click to collapse
weird. =/ Wonder what is causing it.

I've never been able to reproduce this, I wen't on holiday to Australia (no CDMA) for a couple of weeks and kept my phone in airplane mode the whole time using it to read books without a single reboot. Perhaps it only does it on some hardware. Can somebody get a /proc/last_kmsg after a reboot and also do:
logcat -b radio > /sdcard/radiolog before a reboot.
Thanks,

dzo said:
I've never been able to reproduce this, I wen't on holiday to Australia (no CDMA) for a couple of weeks and kept my phone in airplane mode the whole time using it to read books without a single reboot. Perhaps it only does it on some hardware. Can somebody get a /proc/last_kmsg after a reboot and also do:
logcat -b radio > /sdcard/radiolog before a reboot.
Thanks,
Click to expand...
Click to collapse
I'd love to since I can reproduce this pretty regularly, I just need stupid-level directions to get you the info you seek.

I just flew to Edmonton recently and it booted upon turning airplane on, however on the ride back it didn't crash. Its pretty intermittent maybe.

Had the same problem on my way out of town this weekend.

Happens every night I leave my phone in Android and put it on my nightstand charger; no signal and I wake up with it either frozen or rebooted into WinMo.

how to fix turning off issue for samsung i9000 ?

I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed

I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.

what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.

Try to flash a custom kernel and see if it the problem is still there

can you tell me or give information what's is 'flash custom kernel' ?

I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.

Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.

Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4

Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...

Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.

Anyone???
Maybe theres another forum that this problem should be posted at??

I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.

hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...

Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).

Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.

hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you

madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.

try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html

Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know

my turning off issue went back and it's getting every time more annoying, I don't know what to do...

[Q] CM7.2 Weird loss of signal

Hello,
I've had this problem a few times lately, basically sometimes if i lose my signal for a minute it wont come back again until i reset my phone?
P990 running the stable CM7.2 ROM. Standard CM kernel and haven't messed around with basebands before.
Anyone else had this problem?
Thank you

Check to see if the Airplane Mode turned itself on.
Also, disable automatic date and time.
I had a similar issue, where if I powered off the phone for some time, then turned it on again, it would refuse to connect to any network whatsoever. This solved it.

I'll give this a go and see if it occures ago thank you!

[Q] Xperia V: Weird behaviour with Cyanogenmod 10.2

Hey, I'm new here, I apologise in advance if I'm posting it at the wrong place. I also searched for similar issues, but found nothing quite like the symptoms I experience.
I have two new Xperia V phones. I unlocked both and installed Cyanogenmod 10.2 on them.
One of them is not doing any problems. The other has the following behaviour: every once in a while, when I leave it untouched for a few hours, it turns itself off. Well, I'm not sure if it's really turned off, but touching or holding the turn on button doesn't do anything. Only after I remove the battery and put it back in place can I turn the phone back on.
I noticed this behaviour happens regardless of whether I leave the phone charged (say, for the night) or it's just lying around for a few hours. I haven't been able to establish any problem pattern (like how much time of inactivity it takes before the problem kicks in).
Could anyone here help with me with my problem or give me pointers on how to further debug it?
Thanks in advance,
alteclanding

Did the problem exist when you run stock firmware?
Sent from my Xperia V using Tapatalk

No, but unfortunately I don't know how relevant it is, as I didn't really use the stock firmware for a long time -- I pretty much installed Cyanogenmod right away (after around 2 days).

alteclanding said:
Hey, I'm new here, I apologise in advance if I'm posting it at the wrong place. I also searched for similar issues, but found nothing quite like the symptoms I experience.
I have two new Xperia V phones. I unlocked both and installed Cyanogenmod 10.2 on them.
One of them is not doing any problems. The other has the following behaviour: every once in a while, when I leave it untouched for a few hours, it turns itself off. Well, I'm not sure if it's really turned off, but touching or holding the turn on button doesn't do anything. Only after I remove the battery and put it back in place can I turn the phone back on.
I noticed this behaviour happens regardless of whether I leave the phone charged (say, for the night) or it's just lying around for a few hours. I haven't been able to establish any problem pattern (like how much time of inactivity it takes before the problem kicks in).
Could anyone here help with me with my problem or give me pointers on how to further debug it?
Thanks in advance,
alteclanding
Click to expand...
Click to collapse
Next time this happens, connect the phone to your computer and see if it's recognized with ADB. If it is, then it's on, which I think is most likely the case, I've seen it happen before; phone goes to sleep and can't wake back up, which doesn't make sense if you installed the exact same ROM on both phones, and are running the same apps, but at least you can check.
If it is on, you can pull a logcat and dmesg with ADB in order to see what's going on, and even reboot the phone without having to take out the battery.

Antiga Prime said:
Next time this happens, connect the phone to your computer and see if it's recognized with ADB. If it is, then it's on, which I think is most likely the case, I've seen it happen before; phone goes to sleep and can't wake back up, which doesn't make sense if you installed the exact same ROM on both phones, and are running the same apps, but at least you can check.
If it is on, you can pull a logcat and dmesg with ADB in order to see what's going on, and even reboot the phone without having to take out the battery.
Click to expand...
Click to collapse
I've been waiting for it to happen again, and today it happened. But connecting it to my computer, I wasn't able to recognise any device with adb. Nothing on lsusb, no kernel messages, phone is completely dead until I take out battery and put it back again.
Is there any way to check logs after the phone has rebooted? Any logs before the last 'crush'?

i've been using tsubasa 10.2 for months and gave me headache for only had 5hrs battery....
it's just only 4days ago i change to this rom using the backup zip option and having back my xperia v battery to more longer battery service...