HI,with respect to user's , admins n DEvelopers i would like to say SOD might be due to the sleep time settings (image attached)in brightness.i might be wrong or might not be,if im wrong sorry in advance n would req. the admins to delete this thread,Tnx to all..
EDIT :
Use mattcfroyo 1.4 (with latest cotulla zimage) or DARKSTONE froyo v1 latest(384ram enabled)
[my preference] with windows rom: chuky gtx/chukydroid/miri17.6
and radio 2.10.50/2.12.50 no echo no robovoice no sleep of death evrything is fine
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Stoferr said:
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Click to expand...
Click to collapse
thats y i let this info to other users let see what happens to them,n i dont hav n SOD problem but i have robotic voice :"S too bad cant get rid off it,can u sggest me a ROM,m using updated tmous ROM n radio 2.12.50.xxx.. tnx in advance.. and lets see what others say with sleep turned of.. and please do share your results... thank u..
Im testing it right now, so far no problems, but it seems randomly whener SOD appears, so i'll just test it a little longer.
Im using the european HD2.
hmm.. Lets see the results of other users also... and please do share ur findings...
P.S: m using TMOUS HD2 and waitin when i can get rid of robotic voice.
Damnit just got it! Well, seems that this won't help It was a nice try tho
i have never had sleep of death its gta be rom and radio related
i tried to help all... thats all.. but tnx for tryin... but i dont hav SOD either.. now dloadin maatcleo+froyo v1.2 n gonna test if it has SOD..
robotic voice is killing me :'(
I've had sleep of death with basically every android build out there.. i don't think it's a setting in my personal opinion. i think it is because it's still in develoupment and the drivers aren't 100% yet.. and i'm sure in time it will be fixed.
I tried it on zimage 7/25 and still have SOD .Some claim they use the new zimage without SOD ,no matter what I do it won't wake up.
the battery is horrible on 7/23 zimage and carrying the charger in my pocket all the time is a pain.
Off topic: I loved the notes on dna u had there
The "Turn screen off" setting is active in my WM. Using German T-Mobile 1.72 ROM, Radio 2.10.50.19_2, Dan's Froyo V1, zImage 25/7.
Using this combination for two days now and didn't have a single SOD during this time... only two or three times a freeze for few seconds, but afterwards Android resumed working.
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Been using dans13 build with cotullas no speddy zimage. My Rom right now MIRI 17.6 and Radio 2.12.50.26. No SOD report here just couple of freezes now and then. Good battery life. I have to say that I disabled the Auto lock in Windows with HD2 tweak. The first time I tried android on hd 2 i got the SOD, but with this combination and disabling the auto lock been running smoothly. just my 2 cents.
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
Well what I don't get is when I started trying Android on my tmo hd2 I didn't get the sod but now I do. if its the screen why did it start now?
Daaaaaaaaaaaaaaaaaaaamn waiting for new zImage... Seems that I have a sharp panel... How can I check this?
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
well now im using miri's v17.6 rom wid radio 2.12 on tmous HD2 no SOD till now although sleep is active in WM...
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
I've read the same but i think a lot of it is just down to individual ROMs & radio builds, as when android started on hd2 everyone said turn off backlight but mine was never on high nor did i alter any settings as when haret kicks in it turns off all windows functions altogether so you can't have any cross network/OS issues, winmo is supposed to be cut off. although saying that if android is only running off sd how can you remove sd and still run android for 1hr or more? but that's a different topic.
If you have a Tmo US HD2 just use Cotulla's 7/23 zimage and you should not get sod. If you use 7/25 zimage, you WILL experience sod! If you experience sod with 7/23 zimage, then the likely culprit is your sd card. Reformat and try again. If that doesn't work, you need to try a different card.
I am using the 7/23 with chucky's rom, and i was fine all day yesterday but this morning i got 4 sod in 15 minutes, and everytime i rebooted after that. I changed my Radio to 2.12.50.02 and i turned off the sleep thing in WM, and so far haven't had a sod in about 3 hours.
Related
Ok I'm using newest energy cht rom radio 2.12.50 and shubcraft froyo android build with 384 zimage....
Heres the problem that I have had all week my phone works fine when I am stationary minimal screen freezes great speed but when I get up and walk with my phone and try to use it the screen freezes almost every time then the entire phone freezes. I have also noticed this on elevator and when I step out of my car.. this is weird and I know it can't be just me as its been going on for a week now.
So to sum it up stationary best phone ever...walking phone dead and I wanna slam it on the ground.
Sent from my HTC HD2 using XDA App
try the desire v5's zimage, no freeze at all
Im having same issues,with all the version i have tried, including V5 aparently this screen freezing is a known issue and makes the use of Android in our HD2 very very frustrating.
ive upgraded my SD to a class 6 and still suffering from it
Im wondering if there is a program that causes it or its just the OS...
in any case We have to be patient ,im sure pretty soon the amazing developers will come with a solution.
might be a screen rotation issue
Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..
miko3d said:
Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..
Click to expand...
Click to collapse
I've just learned to deal. Its better than SoD's or being in Winmo and having to pull the battery out.
I actually noticed it today as I went from a dark room to a very well lit room so Im with u guys it seems its either rotation issue or light sensor issue andvi have no doubt in my mind the devs will have it fixed in no time just didn't see it mentioned anywhere else so figured it was worth a mention. Thanks all I'm so glad I'm not alone on this one.
Sent from my HTC HD2 using XDA App
when in windows mobile make sure to disable all battery and back light settings and in android change blacklight settings and sleep setting to stay on
I am having the same issue - using ChuckyDroidROM + shubCRAFT CM6RC2, basically when I start moving or even moving the phone the touch screen becomes very unresponsive and sometimes even the hardware buttons don't function properly. At first I thought it was just my device until I saw this post...
Think its a bug with manusfreedoms 384mb ram enabled Zimage dident get this problem using past images.
sure it will be sorted next image release.
I thought i was alone in this case too !
We are not a lot with that screen touch lag, so maybe we did something wrong. Here is what i found so far :
-Changing build don't rix the problem
-tried another radio, another rom...nothing.
I tested 27/07 03/08 cotulla zimage, now manufeeedom 382mo zimage-nopc, the problem is still here.
changed from a class 2 to a class 4 and seems to be worse. (!)
You are right, it seems to be worse when i am moving from one room to another so maybe it is gsensor related.
Right now it is hard for me to type that text,
Don't know what to do... buy a class 10 sdcard ?
I just got my HD2 today and got android set up. I'm noticing the same thing as everyone else with the unresponsive touchscreen. It happens every time I tilt the phone to try to change the screen rotation. Usually hitting the hardware button allows it to respond once again, but it happens quite often.
hey hey hey first and formost i see u guys all hav the same issuse what i dont see is ur device info along with the rom, radio, android verison, and the location ur android is stored ... i have the lates verison of droid v5 also energy with cookie full and my radio is 2.8 i believe android is on the sd card and running smooth ... now that the intro is out of the way hav u guys read what was needed , reason askin i found the thread where the question and answer is... and yes u guys are the only ones... now please do a search go up to the first thread of android on hd2, and good day to u all
Wingtytn, can you be more precise in your answer ? I am a quite long user in Xda, always try to help when i know and i never ask a question wich have been answered somewhere. I don't think i have the noob profile you seems to write. If you think about formatting sdcard, of course i did. I have a 2.08 radio, latest shubcraft build with manufreedom 382mo zimage. My rom was changed to a light android dedicated one, the latest chuckydroid rom. Just don't know what else to do and waste a lot of time trying to fix that from myself.
Sent from my HTC HD2 using XDA App
The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App
shu8i said:
The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks a lot shu8i, i will try an older zimage than the 27/07's cotulla.
Edit : Mmh exact same problem with the 23/07 zimage Cotulla_zImage_CABDET_NOSPEEDDY. That is weird.
I will order a clas 10 sdcard and see what happen...
Try the game ”Runners”. It uses both the camera and the g-sensor and freezes mad anytime, anywhere. Huge affirmation to the idea it's a bug of the g-sensor's or otherwize the screen's drivers.
DuperMan
Me too with screen freezes, i had tried all builds and same result. I think this is a problem with SD access because i noticed more freezes as more apps opened in backgroud.
Try to calibrate the g sensor
Found something ...
try disabling auto-rotation feature (settings -> display)
It works perfectly for me now.
Can you confirm that works for you too?
Did you dind a way to calibrate g-sensor on froyo?
Why the auto-rotation feature hangs so much for us?
Sent from my HTC HD2 using XDA App
hardik119 has found out that going to account & sync and disabling background data has stopped his device from freezing and it has also stopped mine afer 1 hours use. Before it was freezing about every 5 minutes. With doing this I have also disabled setCPU, auto screen rotate and removed gsensor.dll in windows mobile. Please try this out and respond if this has worked for you because maybe we can get a perminant solution. Thanks and also thanks to hardik119 for his extensive testing and possible solutions he is finding all the time Android is usuable on my device hopefully will be for everyone else aswel. Also sorry for opening another thread but there doesn't seem to be any action on hardik119's original thread.
maybe suggested solution works...but...wot is android without data background?
If you disable background data, doesn't that like stop gmail and weather and such updating automatically??
leginag said:
If you disable background data, doesn't that like stop gmail and weather and such updating automatically??
Click to expand...
Click to collapse
Yep...sure does..
the_scotsman said:
Yep...sure does..
Click to expand...
Click to collapse
As has been suggested above...that is kind of /fail.
I'd prefer to live with the occasional few second freeze than not have constant updates.
I applied the RC 7 and my screen freezes are gone. Using this image with mattc nexus 1.0 rom,
http://forum.xda-developers.com/showthread.php?t=756513.
Pretty sure he's just looking for testers to confirm the association. That way developers can narrow down the cause of the issue and possibly fix it. Stop whining about the "solution" he suggested.
Touchscreen freezes still exist
No freezing issues as long as you get the right WM build and android port. Mine is 100% freeze free thanks to the awesome devs here at Xda.
I have auto screen rotate on and still no freezing or SOD. I am using Darkstone's 2.1 build full time now.
Fyi.
Sent from my Hd2 using XDA App
Giving some details about your setup, WM Rom, Current android build/zImage radio etc. might help people participate more. Data connection does cause some freezing but if your saying you were getting freezing every five minutes before you turned it off, then something sounds wrong as mostly people are reporting little or no freezing.
You mention the G sensor and this is a known problem and a work around is to calibrate the G sensor in WM before turning on android, this has helped me.
I also find the kernel has an impact, I found freezing in all the undervolted/ overclocked Images, although Michyprimas latest kernel is the best to date, I have not had a freeze yet.
I found that the stock ZImage from 23rd August had no freezes in my setup.
I've no doubt that the sd card is playing some role and you may wish to experiment with changing that.
Im sure you've tried all this but you need to have the latest Hardspl V3. Do a task 29 to wipe your nand. Install a very light WM ROM, Im using my own WM 6.5.5 ROM but there is a better one by Miri V18 extra light and of course the one listed here such as chucky's ROM etc.
Format the SD card before installing the Android ROM.
Use radio v2.12.50.02.
Try Xcelsior ROM when I tested it I found it very stable.
If you already tried these thing and have had freezing every five mins, then I would suspect your sd card, but its just a guess.
There is a thread somewhere by cotulla asking for participants to isolate this problem so you need to submit your findings there (again if you have not done that)
Thanks for the tips currently using maths 1.5b Rom with 23rd kernel
Hspl3 & radio .12 aswel also tried with calibration on the g sensor in winmo and also deleting sensor.dll also using energy light but have also tried with Miri light the only build I haven't tried so far is the one you mentioned so will give it a go. Thanks
Sent from my HTC Desire using XDA App
Hi I can confirm the disable background sync fix works for me.
Running
- Android O.K. v2.6 [Kumars Leo Touch Premium]
- Mattc 1.6
- Radio 2.12.50.02
LondonTownGuy said:
Giving some details about your setup, WM Rom, Current android build/zImage radio etc. might help people participate more. Data connection does cause some freezing but if your saying you were getting freezing every five minutes before you turned it off, then something sounds wrong as mostly people are reporting little or no freezing.
You mention the G sensor and this is a known problem and a work around is to calibrate the G sensor in WM before turning on android, this has helped me.
I also find the kernel has an impact, I found freezing in all the undervolted/ overclocked Images, although Michyprimas latest kernel is the best to date, I have not had a freeze yet.
I found that the stock ZImage from 23rd August had no freezes in my setup.
I've no doubt that the sd card is playing some role and you may wish to experiment with changing that.
Im sure you've tried all this but you need to have the latest Hardspl V3. Do a task 29 to wipe your nand. Install a very light WM ROM, Im using my own WM 6.5.5 ROM but there is a better one by Miri V18 extra light and of course the one listed here such as chucky's ROM etc.
Format the SD card before installing the Android ROM.
Use radio v2.12.50.02.
Try Xcelsior ROM when I tested it I found it very stable.
If you already tried these thing and have had freezing every five mins, then I would suspect your sd card, but its just a guess.
There is a thread somewhere by cotulla asking for participants to isolate this problem so you need to submit your findings there (again if you have not done that)
Click to expand...
Click to collapse
where to fing the original zimages not the overclocked
touch screen freez reason
I nenarly identified the reason of touch screen freezing ,,it is possibly in the touchscreen kernel ,download figure race from market and the touch screen fresez due to random pess of touch screen with both hands ,I think this is the main problenthl
hoss_n2 said:
where to fing the original zimages not the overclocked
Click to expand...
Click to collapse
http://oe.netripper.com/files/htcleo_autobuild/
23rd august is very stable, you also get usb sinc working and HTC sync.
You need to download the corresponding modules to extract the BCM and TUN files for wi fi to work.
Hello and sorry to open a new thread but i find that problem on every build!
Have you notice Wakeup Lag in all Nand builds?
It whant 2 seconds to light up the screen after i press the power (or any other) button.
Also the same lag ii take from sensor when i make a call.
Is that Kernel problem or is from MAGLDR?
I try SD and NAND build's.
Also i find that thread but....?
http://forum.xda-developers.com/showthread.php?t=813000
I have an euro HD2.
Many Thank's for reading and i wish for a fix..
Happy new year to ALL!
Video of my problem:
ausdim said:
Hello and sorry to open a new thread but i find that problem on every build!
Have you notice Wakeup Lag in all Nand builds?
It whant 2 seconds to light up the screen after i press the power (or any other) button.
Also the same lag ii take from sensor when i make a call.
Is that Kernel problem or is from MAGLDR?
I try SD and NAND build's.
Also i find that thread but....?
http://forum.xda-developers.com/showthread.php?t=813000
I have an euro HD2.
Many Thank's for reading and i wish for a fix..
Happy new year to ALL!
Click to expand...
Click to collapse
Flashing MDJ's Revolution HD Super Light v1.0 NAND ROM fixed this issue for me, it's completely unnoticeable on my HD2 now. I had a little bit of lag on the non light one, and always had it on any other ROMs I've tried. So glad it's fixed now
Even with wifi on it doesn't lag, I'm on an euro HD2 also
I have the same problom but someone doesn´t have this problem.
Many of the kernals had this issue in the past for me on the hd2. Good news is iv never had this on gingerbread releases.
Sent from my HTC HD2 using Tapatalk
This doesn't belong here, it belongs in discussion or questions forum.
Just to add though, I haven't experienced any wake up lag.
I still have this issue with my HD2...Sd builts takes about 1 second lag on wakeup...
Nand builds have less than 1 second lag with a green line on the screen... I might try the GingerBread build to see if the problem is fixed!
Just recorded a video (ignore music, heh) showing how this lag is eliminated with my current build. Wake up lag and during call "black screen" is no longer an issue. Just noticed that proximity sensor doesn't work while having the speaker "on" during the call as you can see in the video, but I guess this is normal.
premikkoci said:
I have the same problom but someone doesn´t have this problem.
Click to expand...
Click to collapse
So all the device's is not the same?
Btw i use:
Radio 2.15.50.14
HSPL 2.08
And i install MAGLDR after my Custom cooked winmo rom.
I have the same lag in EVERY build!!
Thank's
ausdim said:
So all the device's is not the same?
Btw i use:
Radio 2.15.50.14
HSPL 2.08
And i install MAGLDR after my Custom cooked winmo rom.
I have the same lag in EVERY build!!
Thank's
Click to expand...
Click to collapse
Even I have this wakeup lag while turning on the screen and during calls on EVERY build. Tried almost every rom on SD. Haven't tried Gingerbread yet. This is the only reason for me not switching entirely to Android. Previously the SD card was blamed for this. But if its still there with the NAND, this should be a kernel issue. The minimum lag was with the RAM built, but nowhere close to WM.
I guess the DEV's never had this issue, so they never fixed it. But as far as I know, there are many many people having trouble with this and still waiting for a fix.
I have this issue with my EU LEO. Is it specific to the EU hardware?
Yeap! It's very weird but yes...HD2 devices are not the same!
As is said on other threads ...My friend gave me an EU HD2 and Android didn't lag on wake up at all!!!!!!!!!!
I upload a video to show my proble in first post.
Sorry for the bad video quality.
we all have the same problem mate! Ok...sorry...the most of us!
ausdim said:
I upload a video to show my proble in first post.
Sorry for the bad video quality.
Click to expand...
Click to collapse
Yeah, I see that extra 1 sec delay. Try this ROM, see if it changes anything.
http://forum.xda-developers.com/showthread.php?t=893675
And this lag gets worse, if something is getting downloaded or installed and I try to turn on my screen. This really sucks when you have to use your keyboard in between the calls if you are not on speaker.
This will be present in every single build.
It needs to get fixed on kernel level...
To tell you the truth guys! I don't mind that 1 second lag on the wake up... My built is the Nand Froyo something(cmn 6.1 nand) I got the BEST BATTERY DRAINAGE.... Before 2 days i had 75% and today i left with 25% with a few calls,sms,wifi!!!! This ROCKS!!!!
secano said:
Yeah, I see that extra 1 sec delay. Try this ROM, see if it changes anything.
http://forum.xda-developers.com/showthread.php?t=893675
Click to expand...
Click to collapse
Many Thanks but i get the same results. I just reflash that build to see but nothing changed.
kundanjuit said:
This really sucks when you have to use your keyboard in between the calls if you are not on speaker.
Click to expand...
Click to collapse
+1 for that. The most annoying think.
projection said:
This will be present in every single build.
It needs to get fixed on kernel level...
Click to expand...
Click to collapse
Yes that is the true but how is gona fix that? Cause the Android cookers may dont have that problem, so didnt care a lot.
I see the US hd2 doesnt have that problem.
I also try your at: http://forum.xda-developers.com/showthread.php?t=897191 with the same results...
Thanks.
No tmous users don't have this issue at all! Maybe we need to change Countries LOL!
arkatis said:
No tmous users don't have this issue at all! Maybe we need to change Countries LOL!
Click to expand...
Click to collapse
Assumption is the mother of all ****ups.
Wait for it to be fixed in kernel, or get the source and fix it yourselves.
Maybe we need to change Country! Kapish?
Hi guys.
Thanks for the great work you guys achieved!
I have been enjoying my HD2 much more these days.
I have been testing and flashing the nand roms on this forum and it seems all the desire roms are giving me a random reboot on my phone.
Not constant but at least twice a day.
I've uninstalled(or not installed any) apps or killer tasks.
The most stable nand rom I used without crashing much was the nexus rom.
Has the bug from Desire creeped into the nand rom based on Desire?
I've searched the forum and it says it could be corrupt data on the SD card
but I've cleared and formatted the SD card many times.
Any ideas what is causing the crash?
One key point is that my phone is in a flat where the signal is not very good so it is constantly looking for signal from the provider.
Apart from that I have all the HARDSPL 2.08, MAGLDR 1.11 installed and never had a issue flashing the roms.
Any advice or solution would be grateful! Thanks~
are you using an overclocked kernal? cause sometimes it happens when you are using it at full speed and starts rebooting itself, imho...
+1 on the Kernel theory here... Not all silicone is created equal, some phones can take the OC, some can not. Try and throttle it down with SetCPU.
Are you freezing up before the reboots??
---
Sent from my HD2 DROID.
redevilz said:
Hi guys.
Thanks for the great work you guys achieved!
I have been enjoying my HD2 much more these days.
I have been testing and flashing the nand roms on this forum and it seems all the desire roms are giving me a random reboot on my phone.
Not constant but at least twice a day.
I've uninstalled(or not installed any) apps or killer tasks.
The most stable nand rom I used without crashing much was the nexus rom.
Has the bug from Desire creeped into the nand rom based on Desire?
I've searched the forum and it says it could be corrupt data on the SD card
but I've cleared and formatted the SD card many times.
Any ideas what is causing the crash?
One key point is that my phone is in a flat where the signal is not very good so it is constantly looking for signal from the provider.
Apart from that I have all the HARDSPL 2.08, MAGLDR 1.11 installed and never had a issue flashing the roms.
Any advice or solution would be grateful! Thanks~
Click to expand...
Click to collapse
I have the same problems.
I dunno
Now how would I check if I am using the overclocked kernal on my phone?
DroidTh3ory said:
+1 on the Kernel theory here... Not all silicone is created equal, some phones can take the OC, some can not. Try and throttle it down with SetCPU.
Click to expand...
Click to collapse
Not just overclocked kernels, undervolted kernels also don't work well for some people.
OP: which build are you currently using?
Install SetCPU and dial it down a little. If you don't know chances are you are not OC'ed, but that doesn't mean your CPU isn't taking some pain. Bring it down to say.... 800 and see if it holds on. Worth a shot.
---
Sent from my HD2 DROID.
Okie thanks for the quick reply
Currently I am running DFT stock Desire rom.
I think I flashed the phone with every nand rom on this forum....lol
The phone will just reboot when left alone.
So I don't know if it is crashing or freezing.
Sometimes it reboots while charging and sometimes just on standby doing nothing.
Doesn't seem to be getting warm but maybe I can't really feel it as it is bloody cold in my room.
I will try the SetCPU option and see what happens.
It may as well be something that simply occurs randomly. I flashed jdms nand 2 days ago & it worked great, yesterday tho I had to reflash wm coz I needed to reinstall copilot & deactivate it so I could get it on android. Once I went back to jdms nand, I started getting random reboots. So I went ahead & reflashed a 3rd time & its been stable once again.
sent from my HD2 android
It may also be just something it does early on, give it some time to settle...
sent from my HD2 android
i dont have this problem, i testing my rom on 3 days without sim-card. And it work well.
Thanks for the help guys!
Dialed down to 806 MHz.
I will report tomorrow if it reboots or not.
I get really jumpy when my phone suddenly vibrates on me...lol
i had it 2day for the first time, dont know why . im using the standerd rom from cotulla. i had it on the table while i was on my laptop n suddenly
it reboot itself
Yeah its scary coz you never expect it.
Imagine you are on your own watching the Ring or something and the phone jumps up!-_-;;
also keep in mind that your mainboard in the hd2 could be the problem. Had those reboot issues in winmo 6.5 (sometimes when doing nothing but mostly when watching youtube/cpu intensive service).
So i sent my phone to a repair center, they replaced the mainboard and since my phone doesn't reboot > sod whatever again and believe me there are an load of faulty mainboard around sadly
Second that, this girl had the same problem and she just got a warranty phone (new)
Sent from my HTC HD2 using XDA App
I had no problem what so ever when using windows rom, and I used whole bunch of them.
Had freezing from time to time but never reboot issue.
I've searched and there is a whole forum and issue on the HTC Desire rebooting constantly....
The phone rebooted itself just now even with the 800mhz drop.
I am going reflash to stock wm rom and then back to the most stable Nexus Android rom and see what happens from there.
Those of you who haven't had this problem yet let me inform you that this problem doesn't start right away after you flash the rom, maybe couple of days or a week after it started.
Let's try and get it sorted out~!
same problems here, using mdj gingerbread 1.3
but its always freeze while running heavy cpu load apps like games, earth, youtube etc
tried donwclock to around 800 mhz but dont solved =/
Same problem here , randomly reboot.
I m using JDMS 1.62 , only happen on android , WM rom is working fine without reboot.
Well it seems I am not the only one having this problem here.
Anybody running Nexus rom and still having random reboot issues?
Or anyone running Android on SD card without and random reboots?
Could it be the the data on the phone is rewriting the wrong information and causing it some process to fail and to reboot?
It doesn't seem to be the hardware fault(then it would happen alot more often as hardware fail will be permanent and problem would show more frequently) although I have read on the Desire forum people have been sending their phone back for motherboard replacement with mixed results.
Currently reflashing again!
hi all
i have been using nand android builds since day one , and in most of the builds i am having this same issue
sometimes when i receive a phone call the system just hangsout and then gives me a force close msg for the phone application !!
either way , if i force close or not , no further phone calls can be answered and the phone will freeze for about 30 seconds with every call
also when this happens the volume buttons wont modify the volume for the media anymore and the phone wont give any sounds
so is there something i can do to get rid of this ?
i tried android builds based on 2.3.3 and 2.3.4 , miui , sense , no sense , and i have this issue with all of them
again , it happens like 10% of the times
hope i get an answer to this
I want to ask what exactly rom are you using (does it use newest tytung r10 kernel?) and tell you that I have not been experiencing these issues with NexusHD2 2.8 rom (2.3.4).
fpu
i tried typhoon , rafdroid , ndt miui , and plenty more and i think typhoon and ndt miui has the latest kernel
have you ever tried receiving a phone call while the camera application is running
this seems to trigger the issue many times , not always tho
if you have the call recorder running turn it off. it was causing me lot's of problems.
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
domenukk said:
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
Click to expand...
Click to collapse
+1 Same ****...
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
I just recieved a phonecall without problems.
Flashed the .12 radio from http://forum.xda-developers.com/showthread.php?t=611787&highlight=radio
however... My rom feels a bit slower now.
I am playing with it now.
Maybe clearing Dalvik cache will help. Or the issue comes back... Will see.
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Synthezys said:
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Click to expand...
Click to collapse
Switching Radio to something.12 did the trick for me.
No problems for two days now.
domenukk said:
Switching Radio to something.12 did the trick for me.
No problems for two days now.
Click to expand...
Click to collapse
Leo_RADIO_2.12.50.02_2 - is this good?
Synthezys said:
Leo_RADIO_2.12.50.02_2 - is this good?
Click to expand...
Click to collapse
Yes that's it. Works fine for me
Mea culpa just today I had the same issue, for first time.
It's nothing major and reboot made it work fine again, but breaks my belief in HD2 as perfect, native-like Android device.
[email protected] said:
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
Click to expand...
Click to collapse
Beside changing of radio, THIS seems to be interesting.
I'm on MAG but considering switching to cLK (for many reasons - fastboot support being one, second that I don't need 99% of MAGLDR features).
Let's see how it all pans out ;-)
fpu
It just happened again! On the new rom... :/
There is a thread, however, stating that it's due to skype.
This can very well be true.
http://forum.xda-developers.com/showthread.php?t=1164058
but I need skype to stay on contact with my girlfriend... why can't android support skype natively instead of sipthings? -.-
Well still... anyone tried clk (instead of magldr) and skype?
Disable "Audible touch tones". It's under Sound in Settings, it did the trick for me.
I thought this was against robot voice?
well what ever. let's give it a try. Thx
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
An0n1mUs said:
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
Click to expand...
Click to collapse
For me recieving a call does nothing but a very bad noise. hd2 nearly freezes after that. I cannot hang up most of the times. If I somehow manage to, phone app forcecloses and connection cannot be reestablished until I pull out the battery...
Good old Robotvoice. I wish that was my problem.
i have switched to cLK about 3 days ago and till now i have got no problems at all