Database Users

Walking dead.... I can't be the only one

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

Just an answer to my question.

Phone freezes no matter what I try. Stumped
I have a question that seems not to be able to get answered where ever I post it. so please forgive me for posting here if this is not the correct place. I have been trying android from the beginning and I've tried everyones builds. from winmo to droid and different radios to find the right combination. The problem i keep running into is that my phone freezes up no matter what i do. I tried the letama .2 & .3. This problem even occurs in winmo even with the sd out. I may get a full day out of it with no problems then the problem returns. Right know i'm running MDJ Froyo revolution v.1.3 and winmo ozrom 5.10 wwe and radio 2.10.50.26. Also, wipe the sd clean every time i switch builds or upgrade. Haven't figured out how to do logs yet. still searching and reading to try and teach myself how to be more useful around the forums. Thanks and I appreciate all the hard work the DEVS put in. That's why i follow the rules except this time.

cwsmall said:
That's why i follow the rules except this time.
Click to expand...
Click to collapse
Obey the rules!
Naa, just kidding. But if your phone's freezing even in WinMo there's something really messed up. Did you try to make a task 29 and flash your ROM again? That might be helpful.. If not, turn your phone back to original standards (ROM, HSPL, Radio must be as given by the factory) and go to your retailor to use your guarantee if you still have.

Obey the rules!
Naa, just kidding. But if your phone's freezing even in WinMo there's something really messed up. Did you try to make a task 29 and flash your ROM again? That might be helpful.. If not, turn your phone back to original standards (ROM, HSPL, Radio must be as given by the factory) and go to your retailor to use your guarantee if you still have.
I like you sense of humor. thank you for taking the time and commenting. there has been 30+ people that have viewed this and haven't even responded. But, some can ask like where is the download link and we all now where its at. always at the beginning of the thread,but they get all kind of replies. It just makes no sense to me when someone has a legit question they can't get much help. don't really understand that. Thought we were here to help each other.I don't believe that its an issue hardware issue. i believe its more software than anything. It comes and goes. My phone was going thru a period where it would reboot all by itself with no apparent reason. Then all of a sudden it stopped it and hasn't done that for 4 to 6 weeks.

really 97 views and no insight.

you tried the stock factory rom?? It might be hardware. You will be surprised a tiny drop of water inside your phone will slowly mess up your phone through a long period of time.
Are you on tmobile? I will try to look for a stock rom for you.
BTW, what do you mean by freezing? it hiccups or you have to do a battery pull.

cwsmall said:
really 97 views and no insight.
Click to expand...
Click to collapse
btw, your title is a curious one, that is why you have many views and received little to no response. If they can't help you they won't post anything. But I will try my best to see whats going on.

if your suffering from the freezes in winmo and android then you I think that you need to forget about android for the time being and concentrate on getting a stable WM set up........
If you havent already done so then try a hard reset and see if that helps.......
try booting and running your phone with and without your sd card........
with and without your sim card........
if it still happens after the hard reset then you will need to reflash your WM rom, if you plan on using the phone mostly for android then I would opt for a basic rom like the energy reference series or one of duttys roms.....
there are many reasons why your phone might freeze and you need to spend time trying all situations to figure out what makes it freeze..........
if it still happens after the reset/reflash then we can only assume that it is a serious problem which may well require a warranty replacement.....

if your suffering from the freezes in winmo and android then you I think that you need to forget about android for the time being and concentrate on getting a stable WM set up........
I have tried all that you have suggested. The curious thing to me is that it seems to come and go. It first started with the energy rom and it's also happened with dutty's as well. if you guys know how to pull logs that devs need is possible you could give me a run down on how and then maybe i can find out if it is hardware. My phone has never been near water. i'm very careful about that. I'm using ozrom now. This is the 3rd HD2 i've had. the last one lost all touch response. I just have a feeling its software, but i just have a gut feeling on that. Thanks everyone though for your input i greatly appreciate it and keep it coming.

BTW, what do you mean by freezing? it hiccups or you have to do a battery pull.
I have to pull the battery. Then i may have to leave it out for a minute or two maybe longer then replace battery before it will load windows. it will just show the splash screen.

was this happening even when you were running the stock rom?

Have you tried to reformat your SD Card? I have two, and when I used my original card received with my HD2, TMOUSA, it would freeze. Since I reformatted and use new and old card, no problems for over a month.

was this happening even when you were running the stock rom?
YES

Have you tried to reformat your SD Card? I have two, and when I used my original card received with my HD2, TMOUSA, it would freeze. Since I reformatted and use new and old card, no problems for over a month.
yes. I have two the 16 that came with it and an 8. it happens with both. I reformat every time i switch builds.

I see that your using radio 2.10 and that caused my HD2 to freeze a lot. change your radio to 2.12 or 2.14
I use the same Android build as you but with the elegancia gtx wm rom with radio 2.14 and after upgrading the radio the freezing (SOD) stopped.

I started using the radio 2.15.50 and have had no problems whatsoever. Also unchecking auto rotate and auto britghtness helps. Sometimes redownloading and installing your Android helps if you got a bad download the first time.

Update
now runnning enery extreme from 11/5 and mdj desire hd with his newest kernel smartass and the only time it freezes in during a call. usually anywhere from 5 - 15 minutes into the call. Anyone have any insight two a possible solution?

This is what I would do:
1. Task 29
2. Flash a slim WM ROM such as the one mentioned in my signature.
3. Flash a NEW RADIO...at least 2.12 or even higher.
3a. Install NOTHING. NOTHING AT ALL. Just answer and make calls. Period.
4. Test that build for two days. If I have freezups, then my phone is bad and I would flash the stock rom and radio and return it. If it does not freezup goto 5.
5. Completely reformat my SD card to Fat32 32kb (or 64kb if you think it affects stuttering in music).
6. Since you and I are both in the US, I recommend getting an Android that has a built in TMO MMS fix such as the new MDJ build (with link to MMS fix) or the fine MooMoo build or even Bluetopia.
7. Test the basic features in Android for two days minimum and see if I get freezeups (after disabling auto-rotate and wi-fi on the Android build as well as completely shutting off all radios in WM).
8. Be glad I got this far, and slowly reinstall my apps, testing each thoroughly for freezing.

This is what I would do:
1. Task 29
2. Flash a slim WM ROM such as the one mentioned in my signature.
3. Flash a NEW RADIO...at least 2.12 or even higher.
3a. Install NOTHING. NOTHING AT ALL. Just answer and make calls. Period.
4. Test that build for two days. If I have freezups, then my phone is bad and I would flash the stock rom and radio and return it. If it does not freezup goto 5.
5. Completely reformat my SD card to Fat32 32kb (or 64kb if you think it affects stuttering in music)
Thanks for taking the time to post this i appreciate it. I have tried it all. It appears to be getting better. I have been using MDJ's kernels since he posted them with his desire hd build. I have always felt that it was software related and not hardware. It appears to me to be caused maybe by the data drops from ppp. Not sure though till i teach myself how to do that. thanks again though.

Turned out to be a hardware issue. Got my new replacement and it works flawless. Can't believe the fun I was missing. At least it was a great learning experience.
Sent from my HTC HD2 Desire using XDA App

[Q] [help] G-sensor problem

Hi,
I'm using a Tmous HD2, Energy for WM, shubcraft 1.5 for Android.
G-sensor worked fine in both OS, until one day I got stuck with the rain without the raincoat and my HD2 was wet a little bit. I dried it for one night. Everything still works ok but the G-sensor in Android.
I checked it again in WM. There's no problem with G-sensor (I can play games with it or rotate the pictures in gallery tab), but when I turned back to Android the problem still there so I assumed that it should be software's trouble. I booted again into WM, tried to do the callibration, turned on and off the G-sensor. Android's g-sensor kept not working. Home screen (Launcher Pro), browser, games, etc. can't use it either.
After that I downloaded another ROM of Android (JDMS 1.5), erased the old one, hard reset WM's ROM, installed JDMS 1.5: it didn't work as well.
What I haven't tried yet is trying another WM's ROM or re-installing Hard SPL.
So what do I need to do now?!

Can any one help me?

already reinstalled HSPL 3, nothing happened.

Vladikox said:
already reinstalled HSPL 3, nothing happened.
Click to expand...
Click to collapse
Did you try having Android build a new data.img just to test default settings?

jmmmmm said:
Did you try having Android build a new data.img just to test default settings?
Click to expand...
Click to collapse
I have deleted all of Android's files in SD card, then copy the original one --> problem not solved.

I am having the exact same problem. The G-sensor works in WinMo but not Android. I've tried re-formatting the SD card and doing a fresh Android install.
Were you ever able to find a solution or does anyone else have any other ideas of things to try?

My problem has been solved few weeks ago.
At that time I was going to lose hope and came to a decision of giving up trying and willing to say good bye to Android's g-sensor. I turned off the auto-rotate in Android for (about) a week. One early morning waked up, turned it on again and a wonderful thing happened: it was in land-scape mode.
In next few days the sensor was not working so well (but at least it worked). Now it run smoothly and I don't get trouble with it anymore.
Wish you can fix it successfully!

I've got the same problem since i'm running android, tried various winmo versions and HSPL versions without succes. Been trying many different android versions, but all won't work. The strange thing about it is that even the app sensordebug shows no variables. The HD2 had a screenreplacement in the past, but to my knowledge this should have nothing to do with this problem.
In winmo it's working great though.

pvdw50 said:
I've got the same problem since i'm running android, tried various winmo versions and HSPL versions without succes. Been trying many different android versions, but all won't work. The strange thing about it is that even the app sensordebug shows no variables. The HD2 had a screenreplacement in the past, but to my knowledge this should have nothing to do with this problem.
In winmo it's working great though.
Click to expand...
Click to collapse
Yeah, I don't get any variables in sensordebug either.
Actually, I did just replace the glass on my HD2, but I can't think of a good reason why that would make the G sensor not work just in Android. If I had broken a physical part of the phone I would think it wouldn't work in winmo as well, but everything works fine there.
As far as I know, the only physical part that would be used differently in Android would be the SD card, so this has me stumped.
I have also been having a ton of "black screen of death" freezes in Android since replacing the screen. Have you found a build that is at least stable?

I've also got this issue after installing a new kernel and no matter what combination I use now it won't work again. I've tried all of my previous working combinations and none of them have fixed this, I've tried turning off auto-rotate and on again but again nothing happens. This is pretty useless if it's stopping on multiple people for no reason.
Anyone know the script in g-script lite to enable and disable the g-sensor to see if this works as I've used this in the past on one of darkstone's builds but don't have the script anymore?
Thanks

RenaissanceMan said:
Yeah, I don't get any variables in sensordebug either.
Actually, I did just replace the glass on my HD2, but I can't think of a good reason why that would make the G sensor not work just in Android. If I had broken a physical part of the phone I would think it wouldn't work in winmo as well, but everything works fine there.
As far as I know, the only physical part that would be used differently in Android would be the SD card, so this has me stumped.
I have also been having a ton of "black screen of death" freezes in Android since replacing the screen. Have you found a build that is at least stable?
Click to expand...
Click to collapse
I'm using Sergio's core droid V0.8 desire wich is very stable and the camera is working, but I tried many others and I never had any BSOD's.
Can anyone tell us where the G-sensor hardware is located in the HD2? there should be a logical explanation to this problem.

Found something interesting just now, I've tried everything to get my current build working with the G-Sensor again including a fresh data.img and fresh install altogether with no success but decided to install a different build that I had on my PC and the G-Sensor works perfectly. I don't get why it wouldn't work with my current build but will with one thats months old with the same kernel as I'm using now. I've gone back to the newer build and the G-Sensor still doesn't work so I'm just going to use a different build as something's clearly wrong with this one.

AvRS said:
Found something interesting just now, I've tried everything to get my current build working with the G-Sensor again including a fresh data.img and fresh install altogether with no success but decided to install a different build that I had on my PC and the G-Sensor works perfectly. I don't get why it wouldn't work with my current build but will with one thats months old with the same kernel as I'm using now. I've gone back to the newer build and the G-Sensor still doesn't work so I'm just going to use a different build as something's clearly wrong with this one.
Click to expand...
Click to collapse
Huh, what build does it work in for you? I'm using NexusHD2-FRG83D V1.7 and it's not working for me in that or in V1.6 that I was using before.
Also, the black screen of death issue I was having wasn't related, as it was fixed with a radio change.

RenaissanceMan said:
Huh, what build does it work in for you? I'm using NexusHD2-FRG83D V1.7 and it's not working for me in that or in V1.6 that I was using before.
Also, the black screen of death issue I was having wasn't related, as it was fixed with a radio change.
Click to expand...
Click to collapse
It wasn't working in MDJ HD 3.7 build but is in MCCM Froyostone 3.4 and also the version I had from months ago Darkstone Froyostone 3.1.
Funnily enough after a day of using the MCCM build I've just gone back into the MDJ one and it's working again. I did find that my sensors.qsdk8k.so file was named incorrectly in system/lib/hw so check this as well as may have had something to do with it. It was called sensors.qsdk8kso before and had the . missing before the so. Use root explorer to change then reset.
Hope this helps.

AvRS said:
It wasn't working in MDJ HD 3.7 build but is in MCCM Froyostone 3.4 and also the version I had from months ago Darkstone Froyostone 3.1.
Funnily enough after a day of using the MCCM build I've just gone back into the MDJ one and it's working again. I did find that my sensors.qsdk8k.so file was named incorrectly in system/lib/hw so check this as well as may have had something to do with it. It was called sensors.qsdk8kso before and had the . missing before the so. Use root explorer to change then reset.
Hope this helps.
Click to expand...
Click to collapse
I don't have a "sensors.qsdk8k.so" file in that directory, only a "sensors.mahimahi.so". I have other qsd8k files, like "lights.qsd8k.so", so I would think I should have a sensors one as well.
Where does that file come from/where can I get it?
thanks for the help!

Up .......

RenaissanceMan said:
I don't have a "sensors.qsdk8k.so" file in that directory, only a "sensors.mahimahi.so". I have other qsd8k files, like "lights.qsd8k.so", so I would think I should have a sensors one as well.
Where does that file come from/where can I get it?
thanks for the help!
Click to expand...
Click to collapse
I've never seen any files called that on my device so what I'd try is first make a backup of that file then rename it to sensors.qsd8k.so and then restart. All of my files in that folder are all .qsd8k. With some builds/kernels they name things differently and say to rename according to your device for example when you get lights.htcleo.so which you need to rename to lights.qsd8k.so to make it work. If this doesn't work definitely try a different build to see if it's working in that and if it is try going back to your one you're on now and maybe it'll wake it up again.

Hi, I have same problem with sensors on my HTC HD2.
A downloaded Sensor Test app from Marketplace and it give me this values:
Accelerometer (BMA150)
Accel X Waiting... M/S
Accel Y Waiting... M/S
Accel Z Waiting... M/S
Magnetic Field (AK8973)
Mag X Waiting... Deg
Mag Y Waiting... Deg
Mag Z Waiting... Deg
Orientation (AK8973)
Az Waiting... Deg
Pitch Waiting... Deg
Roll Waiting... Deg
Proximity (CM3602)
Near/Far Waiting... Prox
Light (CM3602)
Light Waiting... Lux
Battery
Charge 94 %
Temp 35 Deg
Voltage 4.1 V
It looks like a problem with some communication bus or something like that. Can someone try Sensor Test app and check values.
All of these sensors are not working and I dont know how to fix them
Last edited by pawlish; Today at 02:57 PM..

I'm in the same boat as yall. Sensor works in WM 6.5 and even Windows Phone 7, but still no Android. I have also noticed that the proximity sensor isn't working as well. Do yall think the 2 might be related?

[Q] Auto Reboot/Restart Issue/problem on android boot

Hi there! after googling a lot, and looking here and there around the forum's threads, i found no solution to this one....
I'm quite new at all this so i might not make myself clear enough.
I am using stock winmo HD2 Rom (the october 2010 ROM Update for EU) with 2.15 radio version.
So far have tried only Mdeejay's roms yet still i will try the rest to confirm the problem exists.
So on the first load of any of the version's i've tried (even after swapping kernels and trying different sizes of data.img file) android boots perfectly, runs amazingly smooth, fast, battery long lasting and so on (thanks to MDJ for all this), yet! i've seen many people have the same problem: After some random time (maximum of a few minutes) the phone reboots automatically thus taking you back to winmo.
It's not that i don't like winmo, it's just that i thought someone had found a solution to that.
So.... any clues?

mine is more of, turns off automatically. I thought the battery is dead (or the batt meter/notification is inaccurate) only to find out that it just turned off automatically.

have you tried checking the Q and A section rather than the Development thread???

2 solutions = Format sd card. if problem still persists than you need a custom winmo rom. I suggest elegancia. My setup in my signature runs without a hitch

iv never expierience this, i do get the coma bug, but iv heard a newer radio fixes that so im about to update mine

jose makalolot said:
have you tried checking the Q and A section rather than the Development thread???
Click to expand...
Click to collapse
Sorry, was in a rather hurry and mistakenly posed it here, please admins could you move this?

I have the same problem.
At first the reboot was performed afeter a while, from 30 to 15min, and then it quickly began to reboot after a short time, around 5min. Now, the reboot is performing during the loading process of Android.
My winmo ROM is an Energy 23699 from 24th Nov, but the problem was present while I was in Energy ROM 21xxx from October one month ago.
My Radio is 2.07.50_27.2 flashed 5months ago, no issue with it.
My Android ROM is the llast Froyo with Sense from Darkstone (17th october).
I didn't formatted my SD Card because I wanted to know if there was some boot log somewhere in order to check the problem.
I can't use Android on my HD2 I am sad..

xnnc said:
I have the same problem.
...
I can't use Android on my HD2 I am sad..
Click to expand...
Click to collapse
I am satisfyingly using android on my HD2 using a stock ROM.
I guess that the problem exists on using some of Android Kernels on some HD2s
I found my solution by using "evo carbon remix" currently using v.0.3.1 with Hastarin r8.2
I have not updated nor nothing, having a great battery life and all looking more or less the same as Mdeejay's rom.
I hope this works for you too!

@jsacp : Thank you for the advice, I will try later when I will 100% switch to android.
Well I think I have found the problem. My data.img was 256Mo and I have installed a lot of applications lately, maybe I ran over memory. I replaced the 256Mo data.img with the 1Go data.img which was present in the archive of my Android ROM, and Android didn't have reboot since then. But, of course, I lost all my setup, preferences and applications, I knew it before doing the jump, but glad to see Android back on my HD2
Hope it can help.

Did you notice if your phone feels hot at all? Last time I had a reboot I was downloading stuff with the phone plugged in and it got really hot and restarted. Was an older kernel tho and I think it happened when ppp connection got stuck.
Sent from my HTC Desire using XDA App

When I undervolt my phone too much, it starts randomly rebooting as well.
My guess is that mdeejay's undervolt is too much for your phone.
Try a ROM with hastarin's kernel, it will probably end the random reboots.

How to fix Android phone automatic rebooting problem
Recently my phone got into trouble, it kept restarting. I had to get out of the boot loop error. My phone was HTC Desire 1818 runs on Android Bravo. I was really frustrated because I had many valuable phone contacts in my phone. I searched everywhere on the, I couldn't find any solution at that time, so the only solution in front of me was to format my phone!. Oh.!.. Error fixed by formatting, but my all data on the phone including my valuable phone numbers lost. After 7 or 8 months my phone again got in to the same auto restarting trouble when I installed WhatsApp in my phone. It was really irritating me to encounter these sorts of wretched errors on Android. But at this time I found a good solution. This solution is available and applicable for all Android phones, and Tablets regardless of models and companies.
The solution is simple, Simply Switch on your Android device in 'Safe Mode'
See the Explained Tutorial on How to fix Android auto-rebooting problem going below link
mobihackman.in/2014/02/fixing-android-automatic-repeated-booting.html

[Q] Is anyone suffering from constant reboot after Nand flash?

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!