Database Users

Weird freezing on htc hd2 android 2.2 sense

Im using darkstone's android version on my htc hd2 tmobile 1024mb with 2.12 radio, hspl 3, newest chucky rom gtx lite and every once in a while my phone would freeze up for about 10 secs then resume functioning. This is very annoying and frustrating so i was wondering what can i do to fix this?

mine does it too with a completly different rom..
i think it is because when the screen is off it goes into a "sleep" mode where the cpu gets throttled back to save battery..
when you push the button it takes a few seconds for the cpu to load everything up and resume the phone..
its probably because your loading everything off the sd card and its alot slower then the inernal memory.

Fasty12 said:
Im using darkstone's android version on my htc hd2 tmobile 1024mb with 2.12 radio, hspl 3, newest chucky rom gtx lite and every once in a while my phone would freeze up for about 10 secs then resume functioning. This is very annoying and frustrating so i was wondering what can i do to fix this?
Click to expand...
Click to collapse
this is a known issue on all builds thus far.
try disabling autorotation in display settings. this fixes it for some but not for others (me)

thesweeney said:
this is a known issue on all builds thus far.
try disabling autorotation in display settings. this fixes it for some but not for others (me)
Click to expand...
Click to collapse
Some people say problem is less when they calibrate g-sensor in winmo before started android

I've had this issue on every build as well. Usually for me it gets worse progressively to the point I have to un-install or add a different build. Thankfully when it happens there's a build that is released that I haven't tried.

mines done the same on all builds tested and I am constantly changing it, but downloading 160MB every 3-4 days is getting a little old... I'm going to look into a faster micro SD card..

I had freezing issues like everyone else but mine was when i restarted the phone at once it loads up it would freeze at the first sync. Other times would be during any game play or any cpu intensive app. i found it to be a combo of things. i realize that the sync freeze was due to the hd2 trying to grab all my 120 emails for the gmail app. so i went and deleted al my emails and it hasn't freeze since. i also disable full weather animation, turn off all unneeded sync like stocks, news, and disable any sense widgets that i did not need, also turn service provider to manual and not auto. My phone hasn't freeze once in 5 days ( fingers crossed) versus 3 or 4 per day before i did this. hope it helps someone

NAND!
Sent from my Android Powered HD2 using XDA App

[Q] Fluctuating battery current!

Im using current widget to record my battery consumption during standby and normal use.
Im using SetCPU with 988max/245min for normal, and screen of 245min/max, and battery <30% at 614max/460min.
Also set Taskiller to kill all apps when I turn the screen off.
Autokiller set to optimum (40,50,60).
Turned off htc sense in WM, and boot up haret when keypad lights are on.
Recently changed my WM rom and radio from ChuckyROM lite to stock 3.14, and radio from 2.12.50.02 to 2.15.50.
Android rom is NexusHD2 v1.6.
I found that I can get my battery current to be 3-7mA at standby, but heres the problem! It will only stay at this current for a while before reverting to 40-70mA as it used to be! This is very annoying as you can tell it saps the battery like crazy. In addition when using the phone normally with wifi on I can expect 250-300mA which I think is a bit high. Playing games gets me about 400mA. These effects happen before and after getting Taskiller.
What else have I got to try!?!?!! Please help!

I've had this problem too - And i've found that switching Bluetooth off and on again will stop it for awhile.... But i'm using MDJ's S4 Kernel, and haven't seen this issue for a little while now.
The biggest issue i've always had is every minute I have 4-8mA, but every so often it'll jump to 150mA+ for a minite or so.... At first I thought it was the weather updating or email syncing, but this drain is happening completely at random....
It's got worse since using MDJ's S4 though !

Yeah I forgot to mention I was using MDJ's S4 kernel. I have exactly the same problem as you as well, the mA will jump randomly to mid 100s, I've turned auto sync off and everything!

I had the same experience with this kernel. Randomly, it would drain 160mA with brightness at min, wifi and 3g off, sync off. I'm not using any setcpu or killers. Hopefully this will be resolved with the next version.

hookguy said:
I've turned auto sync off and everything!
Click to expand...
Click to collapse
I've got sync on... But still happens with me - So can't be anything to do with syncing.
I also have 3G permanently off, but polo735 is also the same, and his still jumps up !
I first thought it was 3G, as in my house, i'm on the edge of 3G reception, and it quite often switches at random between 3G and GPRS, so I have it permanently GPRS. No difference

I've managed to get a reasonably good battery life by changing to shubcraft 2.0 and upgrading my SD card to a 16gb class 6. Previously had a 2gb now I'm getting 3-12ma on standby - not too bad.
Sent from my HTC HD2 using Tapatalk

Hi all,
I have a question about this battery life.
With the latest version of Android builds, do we really needs CeT CPU ?(http://forum.xda-developers.com/showthread.php?t=505419), Or the battery drivers allready do the same job that this Cet CPU?
And, the most important, do you know if we will need it for the Nand, which seems to be coming quite soon...?

It is claimed that you don't need set CPU for the newer builds but I still use it just in case.
Also when nand gets finished you should still use set CPU because it helps maximize the battery you've got.
Sent from my HTC Desire using Tapatalk

Yes I think that there still might be a little difference, I nearly stay the entire week end with my battery, for the first time (without using it to much)

Possible soluition to fix 60mA: Enable GPS and wait for full sync

Hi friends.
I found the following coincedence.
When I install new build aparently CurrentWindget shows 60mA in stand by and no way to fix it to 5-7mA as it should be.
The solution which helps me to fix it is the following:
- enable GPS module in settings
- open Maps and wait for it to find where you are located
- go back to homescreen and put phone to stand by
It should be fixed now to 5-7mA current.
Hope it will help everyone.

I can even leave GPS module on all the time after that - standby current stays at 5-7mA level.

hlvl said:
I can even leave GPS module on all the time after that - standby current stays at 5-7mA level.
Click to expand...
Click to collapse
Very strange, but very cool if it works for you! I will give it a shot next time I see high battery drain. Thanks for sharing, it will help at least one other person if it helps you.

I've also found that switching Bluetooth off, then back on again, fixes this 60mA drain !

Common misconception: leaving GPS enabled in settings doesn't leave the GPS chip on the whole time. It just means that an app can enable it when it needs to (e.g. when you open Maps). As long as there's no GPS icon in your status bar, it doesn't drain *any* battery.
OT: that trick would be way faster than rebooting! Gonna try if it works for me too.

Really strange solution for this issue. I have the same problem but for this moment have drain about 5mA after quick boot with dualbootloader (wait time 3sec for Android load). For this moment 5mA in standby mode - with any enabled comm modules (WiFi,Bluetooth,GPS).

My experince of fixing the problem(temporary) is not using taskkiller too often, but it not always works

Curarpikt said:
My experince of fixing the problem(temporary) is not using taskkiller too often, but it not always works
Click to expand...
Click to collapse
Don't ever use your task killer again, it only causes problems.

Tried the above however no sucess..........please check out my post and tell me what you think
http://forum.xda-developers.com/showthread.php?t=857606&highlight=battery+wifi
I'm getting better battery life with wifi on

StephanV said:
Don't ever use your task killer again, it only causes problems.
Click to expand...
Click to collapse
Why? I use it a lot...

To solve 60mA problem, each time you want to boot android:
1) when you are in windows mobile, lock the phone and turn the screen off by press end call button
2) wait few seconds and press it again to turn on screen
3) you see lock screen, unlock your phone
4) after that boot your android quickly within 10 seconds! (you can do it by creat shortcut of android on your home sceen)
I test it and solve problem for me on both mccm and mdeejay builds!

Phantoml337 said:
Why? I use it a lot...
Click to expand...
Click to collapse
It was discussed hunderd of times. You dont need to free up mem in android 2.x
It has already a memory management built inside.
The only reason to use a task killer is to close an app that hangs or not properly close itself.
If you continue to kill your processes and backround apps just to free up ram, you will definitively drain more battery becaouse some of that apps will just load again automatically from SD or, when you open again one of them, it needs to load again from SD.

rafpigna said:
It was discussed hunderd of times. You dont need to free up mem in android 2.x
It has already a memory management built inside.
The only reason to use a task killer is to close an app that hangs or not properly close itself.
If you continue to kill your processes and backround apps just to free up ram, you will definitively drain more battery becaouse some of that apps will just load again automatically from SD or, when you open again one of them, it needs to load again from SD.
Click to expand...
Click to collapse
Exactly. And apps not closing properly is still not an excuse for using it. If the app is bad uninstall it or mail the dev to fixit, but don't go around screwing stuff up with a task killer.

Phantoml337 said:
Why? I use it a lot...
Click to expand...
Click to collapse
Me to....i use 2!
Autokiller on agressive,and a taskkiller....never troubles with drain etc

Or everyone check my signiture for my thread on battery drain solution

I think the OP is really onto something here. I tried this trick & my drain has gone from a steady 55-65mA down to around 5. I'm impressed!

Just one question, those of you that having issues with battery drain what WM do u use? I've recently had a problem on my HD2 (no USB) and i installed a stock ROM. Before i had the VBN Droid Reloaded 2 and with Mdeejay kernel current widget never showed me values above 300mA (witch i believe i only saw that value 1 time). Usually i'd get from 1-2mA to 250mA tops. Now i'll never go below 60mA and i've seen the record of 600mA. Today it drain me from 95% to 35% in about 2 hours. A bit too much for my taste...

I always find if you boot Android with Win Mo fully booted, it's over 60mA, but if I use Exceller Dual Boot to boot Android before Win Mo has finished loading, then it's 5-6mA.

Yea man task_killer - problem

Everything is working for me fine, i am using futureShocks MIUI build, the only thing is when i switch on bluetooth, my battery drain is about 60-80 mAh without bluetooth i have 3-6 mAh... no task killer, no setcpu, with other builds like mdeejays sense roms this problem is not !?
Everyone an idea how to solve the problem ?

[13.JAN] standby 60mA - 5 Tips that may help

hey
1.
just use system panel to kill "ALL" processes include system process
then its will be back to normal mA
[well its better then restarting the phone no ?]
2.
Forgetting to disable bt or gps in winmobile
can cause that too
3.
remove with titanium backup CSPeopleSyncService [ thx to fruchtfliege ]
dont like apps that cant be controlled and do what they like
4. same apps make drain more in standby i think cos its not really full standby
5. unmount sdcard when u gonna "put ur phone to sleep"
[this one should help a lot but in testing for 8 hours gonna try it on nites]

that doesn't always work, if you don't isolate the cause then the app will re-open itself at times.

as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...

fruchtfliege said:
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
Click to expand...
Click to collapse
Might be a nOOb question but how do you kill that CSPeopleSyncService process?
I've been suffering from this 6mA for a couple of minutes and going to 60mA thing. Rebooting 'might' work but I don't want to monitor the consumption every hour.

If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative. Some builds have hot rebooting built-in, even easier.
Back in the game in less than 30 seconds, as opposed to the rather lengthy full reboot.

StephanV said:
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative. Some builds have hot rebooting built-in, even easier.
Back in the game in less than 30 seconds, as opposed to the rather lengthy full reboot.
Click to expand...
Click to collapse
LoL just downloaded it. It really says what it does. Click it and the device reboots without a single warning.

lukesan said:
Might be a nOOb question but how do you kill that CSPeopleSyncService process?
I've been suffering from this 6mA for a couple of minutes and going to 60mA thing. Rebooting 'might' work but I don't want to monitor the consumption every hour.
Click to expand...
Click to collapse
the best way is a taskkiller. i'm using systempanel light (included in mdj hd builds), where you can add programs and processes to ignore list. but as i said, changing sync to once a day fixed my problem with 60ma in standby completely! i don't know why

StephanV said:
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative.
Click to expand...
Click to collapse
lukesan said:
LoL just downloaded it. It really says what it does. Click it and the device reboots without a single warning.
Click to expand...
Click to collapse
I think he meant fast reboot. It just kills everything so it's as if you've just rebooted (sort of).

johncmolyneux said:
I think he meant fast reboot. It just kills everything so it's as if you've just rebooted (sort of).
Click to expand...
Click to collapse
No, I mean Quick Reboot. I'm still not convinced this battery drain is caused by certain processes, so Fast Reboot isn't an option imo.

StephanV said:
No, I mean Quick Reboot. I'm still not convinced this battery drain is caused by certain processes, so Fast Reboot isn't an option imo.
Click to expand...
Click to collapse
Fair enough. So you just mean reboot then. Ah well.

No, it's hot rebooting: basically only rebooting Android (it's a little more complex than that).
I used to do regular reboots but they take way longer.

im suffering from this in Desire HD build
wanna kill this permanently without quick reboot (since my ROM is not Deodex) completely.
disabling sync? its all "disabled"

You all might try a different SD card, had the 30ma bug, was 60. Changed micro SD card, re loaded android, now 3-7ma
Sent from my HTC Desire using XDA App

Just saying, I reboot using dev tools: bad behavior-> crash system server. Probably not the cleanest way to do it but it works.

fruchtfliege said:
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
Click to expand...
Click to collapse
Where did 'find' this information?
Without background sync enabled and facebook not even installed it can draw up to 60mA.
I'm not sure it's that single process causing the drain to be honest.
(Please don't take this the wrong way )

For me I think it is after I turn on WiFi and then back off again. It never goes back to 7ish mA. It stays at around 65mA as if WiFi was still on.
I'm using darkstone SuperRAM FroYo v1.5.

strange?
I just found something interesting while using autokiller.
In the processes (i had the high drain again) there was twice the 'android system' mentioned.
I killed one of those entries, and the drain went back to 6mA.
Of course, can't be sure enough so i rebooted the phone, played with it a little and after 10 minutes of standby, i checked again. 54mA.
Again, Autokiller > processes and twice the android system. Killed 1 of them and back to 7mA.
I can't say why this happens, because in older builds (MDJ 2.4 Froyo clean w/ it's own kernel i don't have that issue).
I am no DEV or programmer, but maybe it's something others could test as well? I've been playing with this and trying to find out why this happens ever since the hastarin 8.6 kernel was released and I noticed it only happens with later kernels and mostly on RAM builds.
Just my 2 cents (or local currency my 2 bani )

I found this on other post
DarkStone1337 said:
Lets see how many people will ignore this...
To fix high power drain / usage in standby (60mA or 70mA) disable 'Use wireless networks' in Settings>Location menu. You will now get 7mA or less constantly. I discovered this as the main culprit last night. Also works in other builds.
Click to expand...
Click to collapse

For whatever its worth: On MDJ Froyo HD 4.6 (and earlier builds) I can get 3-6mA in standby but anytime I change the Kernel or framework-res.apk and reboot, standby consumption goes up to around 55 mA all the time. Doesn't matter how many times I reboot.
I've been correcting this by rebooting to WM and recopying all the files in the android folder (CLRCAD.exe, Haret.exe, initrd.gz, rootfs.img, startup.txt, system.etx2, ts-calibration) except zImage (because I'm using a different Kernel than came with the build) and data.img. When I boot back to Android, back to 3-7 mA. I don't know why this works, but it consistantly does. At least for me.

another tip by darkstone:
turn off the "use Wireless" in the Locations Settings help to solve the problem if you are having high drain when you got data/wifi

Any UK DZ users running CM7?

Are there any UK Desire Z owners out there who are successfully running Cyanogenmod 7? I'm running v7.0.3 and it keeps rebooting spontaneously.
???

I have ran CM7 with no problems other as an issue (actually a "feature") with wifi not working with the screen off,
You could try nightlys if you are set on CM7, in fact I think there is a new stable version coming out soon.

Do you overclock?

I have the Canadian version and in the US (if that helps) and have ran Cyanogen 7.0.3, 7.1.0 RC1 and all the nightlies without reboots..
You should try re-downloading and re-flashing to see if that fixes your problem.

I'm currently trying Virtuous G-Lite to see if it helps. So far so good after 7 hours (i.e. no reboots).
I've also noticed that I can now get access to data roaming services (I'm away in Portugal). With CM7 I was unable to access the local GPRS service. Does this maybe suggest a compatibility issue between CM7 any my radio?
May I ask which radio version you are running bombadier?

itm said:
I'm currently trying Virtuous G-Lite to see if it helps. So far so good after 7 hours (i.e. no reboots).
I've also noticed that I can now get access to data roaming services (I'm away in Portugal). With CM7 I was unable to access the local GPRS service. Does this maybe suggest a compatibility issue between CM7 any my radio?
May I ask which radio version you are running bombadier?
Click to expand...
Click to collapse
Aye 04.12 its the latest i think, its in my sig .30 seems to be a good un, try unity its a cool sense rom if u are into that sort of thing,
Sent from my HTC Vision using xda premium

I've been using MIUI for the last 2 days, and Virtuous G-Lite for a day before that, and have had no recurrence of the rebooting problems that I had with CM7. I guess there was a compatibility problem with CM7 and the DZ

bombadier said:
I have ran CM7 with no problems other as an issue (actually a "feature") with wifi not working with the screen off,
You could try nightlys if you are set on CM7, in fact I think there is a new stable version coming out soon.
Click to expand...
Click to collapse
Menu > Settings > Wireless & Networks > Wi-Fi Settings > Menu > Advanced > Wi-Fi sleep policy > "Never".
Fixed!
itm said:
I've been using MIUI for the last 2 days, and Virtuous G-Lite for a day before that, and have had no recurrence of the rebooting problems that I had with CM7. I guess there was a compatibility problem with CM7 and the DZ
Click to expand...
Click to collapse
You probably just had a bad flash. There are thousands of people in the UK using CM7 on their DZ

martonikaj said:
Menu > Settings > Wireless & Networks > Wi-Fi Settings > Menu > Advanced > Wi-Fi sleep policy > "Never".
Fixed!
Click to expand...
Click to collapse
Try it, makes no difference

bombadier said:
Try it, makes no difference
Click to expand...
Click to collapse
Sure you don't have any other settings that would contradict that? That's the only system wide setting to make Wi-Fi stay on when the screen is off. Are you using a different kernel than stock by chance?

martonikaj said:
Sure you don't have any other settings that would contradict that? That's the only system wide setting to make Wi-Fi stay on when the screen is off. Are you using a different kernel than stock by chance?
Click to expand...
Click to collapse
Yip,noticed on quiet a few ROMs that wifi sleep policy is broken and doesnt do what its ment to.
Bug report
http://code.google.com/p/cyanogenmod/issues/detail?id=4232

bombadier said:
Yip,noticed on quiet a few ROMs that wifi sleep policy is broken and doesnt do what its ment to.
Bug report
http://code.google.com/p/cyanogenmod/issues/detail?id=4232
Click to expand...
Click to collapse
Interesting. Seen some complaints in the Nightly thread but I personally have never had the issue.

Definitely not kernel/setting related, a fresh flash of any flavour of CM 7,broken out of the box,which is a shame as I really like it.
When you say you have never had the issue,is that because you have never tried to stream anything with the screen off ?or that that wifi sleep policy actually works?

bombadier said:
Definitely not kernel/setting related, a fresh flash of any flavour of CM 7,broken out of the box,which is a shame as I really like it.
When you say you have never had the issue,is that because you have never tried to stream anything with the screen off ?or that that wifi sleep policy actually works?
Click to expand...
Click to collapse
My Wi-Fi sleep policy works fine. My battery status page shows my Wi-Fi is on 100% of the time, even when the phone isn't awake and the screen is off.

martonikaj said:
My Wi-Fi sleep policy works fine. My battery status page shows my Wi-Fi is on 100% of the time, even when the phone isn't awake and the screen is off.
Click to expand...
Click to collapse
Yeah but does it actually stay on? A good way to test is to try streaming internet radio,I am still connected but after a couple of minutes playback becomes choppy,phone still claims to be connected.

bombadier said:
Yeah but does it actually stay on? A good way to test is to try streaming internet radio,I am still connected but after a couple of minutes playback becomes choppy,phone still claims to be connected.
Click to expand...
Click to collapse
yep works fine

martonikaj said:
yep works fine
Click to expand...
Click to collapse
Ok then I am at a lose to explain this then,could you run a logcat when you are streaming and send it to me? Would like to see how your output differs to mine.

Downclocking.
bombadier said:
Yeah but does it actually stay on? A good way to test is to try streaming internet radio,I am still connected but after a couple of minutes playback becomes choppy,phone still claims to be connected.
Click to expand...
Click to collapse
The Fact That The Radio Continues To Play Means You're Still Connected.
The "Choppiness" Will Be Due To The CPU Down-clocking While The Screen Is Off.
I'm A UK User Running CM7 And All Is Well. WiFi Sleep Policy Is Set To Never And I Always Receive E-Mail Notifications On My Phone Before My PC Notices So It Does Work! I'm Running One Of The Newest Nightly Builds.
Try Running SetCPU And Setting Up A Screen Off Profile To Up The Clock-speed Above Standard As It Goes Very Low When The Screen Is Off.
This Will Impact Your Battery Life But If You Find The Minimum Frequency Required To Eliminate The Choppy Playback You Can Live With It.

OllieD said:
The Fact That The Radio Continues To Play Means You're Still Connected.
The "Choppiness" Will Be Due To The CPU Down-clocking While The Screen Is Off.
I'm A UK User Running CM7 And All Is Well. WiFi Sleep Policy Is Set To Never And I Always Receive E-Mail Notifications On My Phone Before My PC Notices So It Does Work! I'm Running One Of The Newest Nightly Builds.
Try Running SetCPU And Setting Up A Screen Off Profile To Up The Clock-speed Above Standard As It Goes Very Low When The Screen Is Off.
This Will Impact Your Battery Life But If You Find The Minimum Frequency Required To Eliminate The Choppy Playback You Can Live With It.
Click to expand...
Click to collapse
Just to clarify my problem once more, doing anything over wifi with screen on is fine,streaming, uploading to dropbox,etc but after a couple of minutes with the screen off my transfer rate crashes,the wifi is going onto a power save as I am still connected(wifi connected icon still there), CM7 is the only ROM that I have this problem with,I use Unity and with screen off there are no problems,dont see how underclocking affects this as on Unity my screen off clock is 245Mz. I know you use the example of email notification,have you tried uploading files with screen off or streaming?
If that works then could you please send me a copy of your logcat to compare to my output?

I tried it no problems. But i prefer htc sense with android 2.2.
If ive was to choose a different rom apart from sense stock roms then it has to be miui.
Its fast and ui is superb.