Related
It's been brought to my attention that applications keep running when the device is put into standby, while I always thought that the CPU would merely respond to interrupts which might then move it to a higher power state.
Try as I may, I can't find any definition of what is supposed to happen and if this behavior is consistent between the phone edition and the "normal" Windows Mobile or if it's even defined by each manufacturer. I've also surveyed the Power registry tree without finding anything that would tell me what happens to the CPU.
Any pointers to real information greatly appriciated.
as far as i know it's off and only the gsm part is running
and of cause the clock which is running in hardware much like a clock in a pc
of cause i could be wrong
well, no, I have clear indications that it is actually running. It responds to pings for one thing...
well maybe the gsm hardware can do that ?
normal programs are not running though like mediaplayers and programs you made yourself and .......
Rudegar said:
normal programs are not running though like mediaplayers and programs you made yourself and .......
Click to expand...
Click to collapse
No, that can't be the whole truth. If it were, you wouldn't be able to stay signed in on messenger for instance.
I think it just stops most tasks (i.e. all non-system programs, some drivers as those of storage cards, etc.), while some others (notifications, keyboard driver, GSM tasks, ...) are still active. Additionally, the CPU is slowed down as much as possible.
I did some experiments today and here's what I found (on a particular device).
I ran a ping *from* the device to a laptop and sniffed the traffic with Ethereal . When I pressed the power button, what one would expect to happen happened: the pings stopped instantly. After a while I started a ping going in the other direction, i.e. *to* the device. Not only did this provoke a response, but the original pings from the device resumed, but the screen did not turn on. When I stopped pinging the device, the pings *from* the device stopped after a few seconds.
Clearly, the GSM processor is moving the PDA portion to a higher power state, at least briefely, in response to incoming traffic.
Hi,
I'm very happy with my universal (wifi and vga in pocketsize) only one thing is driving me crazy.
every, say once in 10 times the universal won't start when I press the power button. (after it turning off automatically after a few minutes when on battery power). Worse yet, it doesn't accept phonecalls and smses anymore either..so it already crashed silently. Unfortunately you can't see this from the outside since the lights still flash. I only notice it crashed when trying to start the device.
I've updated to wm6 because I thought it was a wm5 issue, but it wouldn't help. I also updated to radio 1.13 (the orange radio stack as found on this site). But this too, didn't fix it.
does anybody else have the same problem?? This problem renders my whole device unuseful. =^(
thanks!
Reinier
Welcome to the club...looks like no solution on this one yet. Here is a link
http://forum.xda-developers.com/showthread.php?t=272938
Some say it might be incompatibility with the SD card, but not in my case.
Hi,
that doesn't sound too good.
Anyhow, I'll experiment with it some more (what else can one do?) to see what is making it crash more or less (wifi/sdcard/simcard/battery?)
I'll post my findings... maybe we can find some mutual thing which might be causing it
I doubt it is software related since my whole machine is wiped clean and has nothing on it
R
yes, me too...and it seems to get worst as time goes by...anyways, I suggest that if you have any warranty left to send it back for warranty. GOodluck!
thats a pretty good point... ;^)
I'll check.
too bad it's quite vague description:
yes, sometimes it doesn't powerup..
you can already see the technicians there... they try it 4 times, it works everytime (of course) , and they send it back with a sticker saying 'correct'
ah well.... lets not get ahead of time.
r
Solutn found...check your PM
Check battery charge level
hi, i didn´t experienced that problem, but when i start up my device, sometimes, the start-up is really slow and the screen gets white but finally, i mena 2 or 3 seconds´ time it becomes normal.
Is that what experienced?
clemsyn said:
Solutn found...check your PM
Click to expand...
Click to collapse
What do u mean with PM?
DId u get the solution?
See ya folks
Solution
Check you PM means check ur private messages
A fellow here with the same problems sent his device for repair and the problem was voltage control unit of mainboard
Solution:
1. Install Pocket Hack Master and go to settings and disable the CPU scaling of the device. Then set it to start at startup. Then clock your device at 312 mhz before turning off the device or closing the clamshell. You can always clock it to 520 while using cpu intensive applications. Just make sure to set it at 312 before turning it off.
thank you buddy
Jumanji1212
Did it also work for you? I forgot to add that I am also using an external charger specifically for Universal because Im afraid charging it via miniusb might mess up the voltage control unit more.
Well, i normally charge it with the ac/dc adaptor but not always. Since i deleted spb diary today plug-in and installed the latest qtek spanish rom and radio, the time of the white-screen shorten.
clemsyn said:
Check you PM means check ur private messages
A fellow here with the same problems sent his device for repair and the problem was voltage control unit of mainboard
Solution:
1. Install Pocket Hack Master and go to settings and disable the CPU scaling of the device. Then set it to start at startup. Then clock your device at 312 mhz before turning off the device or closing the clamshell. You can always clock it to 520 while using cpu intensive applications. Just make sure to set it at 312 before turning it off.
Click to expand...
Click to collapse
Hello, I have the same problem (Power button does not start after an auto sleep).
My qtek 9000 however gives a blank screen when playing with the PHM speed tests. (When it is plugged in it works.)
Now I am a little afraid to do the "set it to start at startup"
Is there no risk it will never startup anymore?
Can I do this (temporaly) just for testing without the auto startup option?
So: disable CPU scaling and set the speed on 312 and put it in sleep mode.
I need my Qtek so badly that I get horribly stressed with this kind of things.
Huib
Hi. i want to ask. what makes PDA hang?
I am currently using Atom Life.
And sometimes it hang. and i have to take out the battery and turn it on again. which is very troublesome and makes some of my sms gone as well.
it sometimes occurs when i turn it on. it also hangs there.
can anybody advice me on this?
thanks.
T3D0nG said:
Hi. i want to ask. what makes PDA hang?
I am currently using Atom Life.
And sometimes it hang. and i have to take out the battery and turn it on again. which is very troublesome and makes some of my sms gone as well.
it sometimes occurs when i turn it on. it also hangs there.
can anybody advice me on this?
thanks.
Click to expand...
Click to collapse
lol,
good question
the buggy Os makes it hang.
a Rom upgrade should solve the problem.
shaileshashar said:
lol,
good question
the buggy Os makes it hang.
a Rom upgrade should solve the problem.
Click to expand...
Click to collapse
however, i updated to the latest rom already. how is it? does RAM affect?
T300,
There are lots of things that can make your pda hang, probably too many to go into. I will try and give you the principal areas you need to address, which come from my own experience coupled to tons of reading on here.
1) Activesync - This has a habit of running all the time and is a prime cause of lockups. Use the fake server solution to solve that problem (search on here for it using google search. I will give you the google search link in a minute).
2) Software incompatibilities - You need to make absolutely sure that if you are running WM6, your apps are the latest version capable of running under WM6. I have had a lot of problems trying to run WM5 apps under WM6.
3) Battery and power locks - Make sure that all system locks are disabled. For example you can set your system to turn of the LCD screen or power of after a period of time. Make sure all of these are inactive/not set. If you want to turn your screen off then lighty touch your power switch and it will do the job for you. Touch it again and your pda springs into life; simple. You can use the device lock option on the today screen if you need to lock your screen with the pda on; no problems with this option.
4) Programmes running in the background - I strongly suggest that you set your pda to completely close down any programmes after you have run them, rather than minimise. Use the task manager option to sort this out or install the htc x-button app (search on here for that also).
5) Beams and Wifi - Make sure these are turned off unless you need to use them. Switch them off as soon as you have finished with them. Benefits are improved battery life and less freezes.
6) Inappropriate themes - Not all themes work happily with WM6. Some do lock up your machine. Keep it simple; load a standard WM6 theme that you know works and leave it at that.
There's more, but this should give you something to work on. I will add to this post as I remember other things.
Let us know how you get on. Google search for XA is:
http://www.google.com/advanced_search?q=+site:http://forum.xda-developers.com&hl=en&lr=&as_qdr=all
Cheers
WB
Roughly 50% of the time when I suspend (sleep, via the Shift's power slider switch) Vista it fails - the screen goes off but then comes on again with Windows rebooting from scratch. I can't find an obvious pattern to it yet. My Vista install is standard, just updated with Windows Update patches (not SP1). Anybody else seen this yet? Any ideas for a solution please?
Thanks,
Andy
I haven't been able to duplicate this problem - I have the power switch set to hibernate, but I do sometimes use standy via the keyboard shortcut.
It always works fine for me.
normaly it's an application running on vista, Outlook 2007 is a real pain regarding this issue.
try to close all applications and see if the problem is still there, if not find out what app. it is by closing one at the time (antivirus etc.)
I have the same problem. I even reinstalled Vista to be sure it was not caused by some software I installed but it's still the same. The problem occurs when I try to enter sleep or hibernate mode.
same here. I havent found a pattern too...... I am running vista sp1. And some times when I resume I see the window you see after bad shutdown, this is, "press x to safe mode, press y to safe mode with network, ", etc
No doubt I'm speaking too soon, but since installing Vista SP1 today I haven't had the suspend problem.
Same issue here.. It thought it had something to do with the hybrid sleep I enabled. Disabling didn't solve it.
Windows reboots and tells it has recovered from a unexpected error, and you can click to determine what caused the reboot. Windows then analyses that the issue has been caused by 'Vista' made by 'Microsoft'.
So I think it's a bug in Vista not fixed in SP1. It's actually very anoying because I like hybernating my device to spare battery.
infraskill said:
Same issue here.. It thought it had something to do with the hybrid sleep I enabled. Disabling didn't solve it.
Windows reboots and tells it has recovered from a unexpected error, and you can click to determine what caused the reboot. Windows then analyses that the issue has been caused by 'Vista' made by 'Microsoft'.
So I think it's a bug in Vista not fixed in SP1. It's actually very anoying because I like hybernating my device to spare battery.
Click to expand...
Click to collapse
This is really becoming very annoying especially because of the short battery life. Sleep and hibernation mode are the only ways to survive a working day on 2 batteries. If I leave Vista on while I'm working in WM6 then Vista crashes after 10 to 15 minutes 2 out of 3 times. We need to find a solution for this problem the sooner the better or I will have to return to my Everun with an extended battery that works for more than 7 hours on one charge.
I don't mean to rub it in, but I'm not having any of these problems. Sleep, hibernate, using WinMo for hours while Vista is running, all working fine.
I've not installed SP1 yet, or the graphics driver update that windows update offered me - don't know if that's relevant.
I haven't installed the graphics driver either so I don't think it's that. I'd love to know what though, I've tried endlessly to find a pattern. It can do it with no applications running just as likely as if I have a few running. Also it is now happening again with SP1. It can happen after a completely clean reboot too - i.e. Vista boots, I log on and try and suspend, and it barfs.
And not mention the HTC Control panel now crashes after SP1 and I found out that the audio out driver is gone after SP1.
I find all of this rather dissapointing it's almost a virgin Vista installation. I have not tweaked it or did strange things to it.
I'm going to reinstall it see if that sets me back to a working installation.
infraskill said:
And not mention the HTC Control panel now crashes after SP1 and I found out that the audio out driver is gone after SP1.
I find all of this rather dissapointing it's almost a virgin Vista installation. I have not tweaked it or did strange things to it.
I'm going to reinstall it see if that sets me back to a working installation.
Click to expand...
Click to collapse
I didn't have these problems.
Out of the box I made a ghost image and then I installed SP1 directly after that.
Sound is perfect, HTC control panel works perfect. No problem with SP1. It's even beter with it (faster. I installed a shift for a customer and I compared the SP1 with the non SP1, so I know where I'm talking about )
I've now restored Vista from the recovery partition and, so far at least, I've had no problems with suspend or hibernate.
Sort it out
I solved all my suspend problems by restoring to VISTA...
Then cancelling the origami install on first boot.
Then installed SP1 before doing anything else.
This seemed to have sorted out the problems.
Blitz
blitzspear said:
I solved all my suspend problems by restoring to VISTA...
Then cancelling the origami install on first boot.
Then installed SP1 before doing anything else.
This seemed to have sorted out the problems.
Blitz
Click to expand...
Click to collapse
So you think it's Origami that's causing the problems?
Hi,
I had no hibernate problems with my shift also none after SP1.
I did have to reinstall Shagctr (vista commanager) and that fixed the sound too.
Also I removerd Origami after my second boot. It is useless anyway...
greetz,
Pfeffa-rah
No hibernate problems on loader or using "balanced"?
Now, first: I am not a technical guy like you guys but ...
--I have the idea that it always hibernates and resumes correctly when on the battery charger.
On battery only:
--That it hibernates/resumes correctly when setting the battery powerplan to "balanced"
--That it always hibernates wrong when the powerplan is set to "power saver"
So somewhere the Power Saver settings are causing the problem?
I will keep testing. It's a boaring Easter anyway.
PLs could you guys check if that is also the case in your situtation?
Huib
herpi said:
Now, first: I am not a technical guy like you guys but ...
--I have the idea that it always hibernates and resumes correctly when on the battery charger.
On battery only:
--That it hibernates/resumes correctly when setting the battery powerplan to "balanced"
--That it always hibernates wrong when the powerplan is set to "power saver"
So somewhere the Power Saver settings are causing the problem?
I will keep testing. It's a boaring Easter anyway.
PLs could you guys check if that is also the case in your situtation?
Huib
Click to expand...
Click to collapse
can you check with the advanced settings of the power saver mode to see which one leads to the issue?
herpi said:
Now, first: I am not a technical guy like you guys but ...
--I have the idea that it always hibernates and resumes correctly when on the battery charger.
On battery only:
--That it hibernates/resumes correctly when setting the battery powerplan to "balanced"
--That it always hibernates wrong when the powerplan is set to "power saver"
So somewhere the Power Saver settings are causing the problem?
I will keep testing. It's a boaring Easter anyway.
PLs could you guys check if that is also the case in your situtation?
Huib
Click to expand...
Click to collapse
I think this could be the cause. I changed the powerplan from 'power saver' to 'balanced' this morning. Since then I didn't have any problems putting my Shift in sleep or hibernate mode. I will continue testing it and keep you informed. But there is hope ...
sonietje said:
I think this could be the cause. I changed the powerplan from 'power saver' to 'balanced' this morning. Since then I didn't have any problems putting my Shift in sleep or hibernate mode. I will continue testing it and keep you informed. But there is hope ...
Click to expand...
Click to collapse
look at the advanced settings in both mode to see what is different please,
it could help us to see what can lead to an issue and what won't.
I Think I May have found the cause of the otherwise apparently 'random' freezes/hangs and total lack of touch sensitivity.
Basically, In my case at least, It Is the G-sensor/accelerometer.
I have been noticing increasing numbers of these freezes on Mattc 1.5 Froyo, Mainly in Landscape, Mainly in games.
TEST:
I installed 'Iron Sight' Game. (If theory is right then you should be able to use any landscape game, but please try Iron sight if possible.)
I Ran the game and it switched to landscape,
SO I PHYSICALLY TURNED MY HD2 TO LANDSCAPE.
THIS IS WHERE THE FREEZING AND LAGGING BEGAN!
On the Main menu found it difficult to press any options.
When I did manage to start a Game The control buttons were hard to press and the game was unplayable because screen sensitivity was just not there most of the game.
I Then Physically turned the HD2 around and Back to Portrait orientation, AND ALTHOUGH THE SCREEN ORIENTATION STAYED IN LANDSCAPE I DID NOT EXPERIENCE ONE SINGLE LAG OR FREEZE.
BUTTON PRESSES WERE RESPONSIVE TO TOUCH AT ALL TIMES FOR AT LEAST 15 MINUTES!
HERES WHERE IT GETS MORE INTERESTING....
I Then Turned the HD2 back around to landscape again and the Problems IMMEDIATELY RETURNED.
I THEN HELD THE PHONE VERY STILL IN LANDSCAPE AND AFTER A FEW SECONDS THE PROBLEMS/LAG/FREEZES DISSAPEARED AGAIN!!!
TESTED REPEATEDLY!
IN LANDSCAPE AS SOON AS THERE IS ANY PHYSICAL MOVEMENT, THE GAME FREEZES, BUT IF I KEEP IT STILL THE GAME RESPONDS PERFECTLY WITHOUT HESITATION.
Can some of you please test this theory?
A cradle/Dock would be handy for testing but it is possible to keep the phone still enough in-hand in my tests.
Use the game "Iron Sight" where possible, but use other games/apps too if you have time or inclination
Post the results below ( with logs where possible ?) Please.
Note:
After discovering the above, I did a search on XDA and found that a member called 'Hinky' and touched on this but I think I have narrowed it down.... I think
Please test and confirm (or debunk lol).
Thanks.
thesweeney said:
I Think I May have found the cause of the otherwise apparently 'random' freezes/hangs and total lack of touch sensitivity.
Basically, In my case at least, It Is the G-sensor/accelerometer.
I have been noticing increasing numbers of these freezes on Mattc 1.5 Froyo, Mainly in Landscape, Mainly in games.
TEST:
I installed 'Iron Sight' Game. (If theory is right then you should be able to use any landscape game, but please try Iron sight if possible.)
I Ran the game and it switched to landscape, SO I PHYSICALLY TURNED MY HD2 TO LANDSCAPE.
THIS IS WHERE THE FREEZES BEGAN!
On the Main menu found it difficult to press any options.
When I did manage to start a Game The control buttons were hard to press and the game was unplayable because screen sensitivity was just not there most of the game.
I Then turned the HD2 Back to Portrait mode AND ALTHOUGH THE SCREEN ORIENTATION STAYED IN LANDSCAPE I DID NOT EXPERIENCE ONE SINGLE LAG.
BUTTON PRESSES WERE RESPONSIVE TO TOUCH AT ALL TIMES FOR AT LEAST 15 MINUTES!
HERES WHERE IT GETS MORE INTERESTING....
I Then Turned the HD2 around to landscape again and the Problems IMMEDIATELY RETURNED.
I THEN HELD THE PHONE VERY STILL IN LANDSCAPE AND AFTER A FEW SECONDS THE PROBLEMS/LAG/FREEZES DISSAPEARED AGAIN!!!
TESTED REPEATEDLY!
IN LANDSCAPE AS SOON AS THERE IS ANY PHYSICAL MOVEMENT, THE GAME FREEZES, BUT IF I KEEP IT STILL THE GAME RESPONDS PERFECTLY WITHOUT HESITATION.
Can some of you please test this theory?
A cradle/Dock would be handy for testing but it is possible to keep the phone still enough in-hand in my tests.
Use the game "Iron Sight" where possible, but use other games/apps too if you have time or inclination
Post the results below ( with logs where possible ?) Please.
Note:
After discovering the above, I did a search on XDA and found that a member called 'Hinky' and touched on this but I think I have narrowed it down.... I think
Please test and confirm (or debunk lol).
Thanks.
Click to expand...
Click to collapse
Yes this is something that the devs have been discussing. It does seem that the freeze issue is in fact related to the g sensor. I don't know if anyone is working on it at this time but I believe Cotulla will try to sort it out for his September release
ala380 said:
Yes this is something that the devs have been discussing. It does seem that the freeze issue is in fact related to the g sensor. I don't know if anyone is working on it at this time but I believe Cotulla will try to sort it out for his September release
Click to expand...
Click to collapse
DOH! Didnt know it was already a known issue LMAO
I'll get my coat....
thesweeney said:
DOH! Didnt know it was already a known issue LMAO
I'll get my coat....
Click to expand...
Click to collapse
Lol keep with the testing though I didn't figure that much out
Hmmm this is def the prob for my touch screen issues. I tested a bit using the latest mattc Leo + Froyo w/Sense 1.5 version, with latest FULLRAM. I found that while on the sense home screen if I hold the phone out in front of me either landscape and portrait it's ok, and I can do whatever I want at full speed no lag at all. THEN if I lay the phone flat, It freezes. I did this like 20+ times and every time It would freeze whether I was playing a game or reading an email.
This also happen to me. Using Mattc 1.5 Froyo, it happens when using internet browser. The screen will freeze or not response right after i turn from Portrait to Landscape or sometimes have to wait for few seconds. I have to turn my device from Landscape to Portrait, and back to Landscape again, then the screen responses back to normal. This also happens in Copilot app when using in Landscape mode.
I turned off the screen rotation
What I did since i installed my ROM with 380mb ram is to turn off all screen rotation settings, so far so good, I haven't notice any freeze or lag so far in any application or while waking the device up, I used to have it and I hate it, I almost went back to Winmo!!.
robrob777 said:
What I did since i installed my ROM with 380mb ram is to turn off all screen rotation settings, so far so good, I haven't notice any freeze or lag so far in any application or while waking the device up, I used to have it and I hate it, I almost went back to Winmo!!.
Click to expand...
Click to collapse
This was the first thing i tried but strangely it made no difference.
anyone know how to totally disable the g-sensor?
doesnt have any of the mentioned problems...
iron sight lite runs the same for me when i hold the phone portrait or LS...
have no bad screen sens while holding LS...
running mattc 1.5 with the default zimage...
thesweeney said:
This was the first thing i tried but strangely it made no difference.
anyone know how to totally disable the g-sensor?
Click to expand...
Click to collapse
I want to know too! disabling auto rotation doesnt mean completely stop the g-sensor running.
Bimme said:
doesnt have any of the mentioned problems...
iron sight lite runs the same for me when i hold the phone portrait or LS...
have no bad screen sens while holding LS...
running mattc 1.5 with the default zimage...
Click to expand...
Click to collapse
Please tell me....
Did you fresh install 1.5 or upgrade 1.4>1.5?
I had quite a few freezes on 1.4.
Then I upgraded to 1.5 and kept my apps etc from 1.4.
I HARDLY HAD ANY FREEZES AT ALL
Then I did a fresh install of 1.5 and started getting LOTS of freezes.
i did a fresh install.
i deleted all android files on my sd card and extracted the new build to a new made "Android" folder...
i use xanny roms, and i still have the robovoice problem, so i can´t use android daily...
i noticed on all android builds ive tried sofar, that the polling interval of the gsensor is very bad/small. U can see it when u go to calibrate the gsensor, the bubbles move very slowly...
this is not a big thing when u only use the gsenor to turn screen to LS, but it is essential to play games using the sensor...
thesweeney said:
DOH! Didnt know it was already a known issue LMAO
I'll get my coat....
Click to expand...
Click to collapse
Lol, no worries I'm glad that you pointed it out. This was actually one of those really useful threads and the kind of thing that the developers are looking for. I am not a dev but I speak with them pretty regularly when the same issue are pointed out time and time again by those who do not read the threads. This was something that has not been talk about here so I appreciate your well thought post and the information that you provided
I was just a step before creating a new thread about it when I saw this one.
This is definitely one of the things that are really pissing me off using Android.
Furthermore, I did tests on this issue for quite long to doubt that it's an autorotation related issue. Maybe it has something to do with the g-sensor, but it still would happen randomly even trying not to move the phone at all. I noticed that the problem wouldnt appear that often when decreasing the polling interval of set cpu and same time increasing the min. freq. to 380, but still, it DOES happen.
I'd really appreciate any statement on this, developer side of course.
I have the occasional screen freeze on landscape, but not very often using froyostone.
Bimme said:
i did a fresh install.
i deleted all android files on my sd card and extracted the new build to a new made "Android" folder...
i use xanny roms, and i still have the robovoice problem, so i can´t use android daily...
i noticed on all android builds ive tried sofar, that the polling interval of the gsensor is very bad/small. U can see it when u go to calibrate the gsensor, the bubbles move very slowly...
this is not a big thing when u only use the gsenor to turn screen to LS, but it is essential to play games using the sensor...
Click to expand...
Click to collapse
Cheers for that ^
+1 for the Gsensor polling intervals seeming very slow.
THIS CAN BE SEEN VERY CLEARLY USING THE 'VR TUNNEL' LIVE WALLPAPER.
Here the cubes move smoothly at a good fps while the tunnel moves around at what appears to be 4/5 fps.
ala380 said:
Lol, no worries I'm glad that you pointed it out. This was actually one of those really useful threads and the kind of thing that the developers are looking for. I am not a dev but I speak with them pretty regularly when the same issue are pointed out time and time again by those who do not read the threads. This was something that has not been talk about here so I appreciate your well thought post and the information that you provided
Click to expand...
Click to collapse
Hehe, Thanks for that ^.
I dont feel quite so stupid now
For a moment there, before I found out it was a known issue... I thought I had discovered the Androids very own penicilin or something equally as important... but as usual I was behind the times lol.
Jealousy said:
I was just a step before creating a new thread about it when I saw this one.
This is definitely one of the things that are really pissing me off using Android.
Furthermore, I did tests on this issue for quite long to doubt that it's an autorotation related issue. Maybe it has something to do with the g-sensor, but it still would happen randomly even trying not to move the phone at all. I noticed that the problem wouldnt appear that often when decreasing the polling interval of set cpu and same time increasing the min. freq. to 380, but still, it DOES happen.
I'd really appreciate any statement on this, developer side of course.
Click to expand...
Click to collapse
Possibly not related to autorotation per-se, but...
With Autorotation disabled... If I turn my phone on its side (with volume buttons pointing towards floor) I still experience freezes on my home screen or anywhere else for that matter.
Plus I have found that holding the phone VERY still in any position seems to eliminate 'ALL' freezing and lagging problems.
Do the G-sensor and the Dgital compass 'interlink' or communicate in any way? Is it possible that the screwed up compass output is screwing with the g-sensor output?
I ask this because the game 'hungry shark' thought that my phone was flat whent the usb port was pointed down towards the floor.
Dont know if that makes sense but for me it seems like the g-sensor is fubar as well as the digital compass.
trilbyfish said:
I then used even bigger and bolder letters to emphasize my points!
Click to expand...
Click to collapse
[SARCASM]Very helpful buddy[/SARCASM]
I did the font size thing for people who just wanted to skim through the long post.
thesweeney said:
Possibly not related to autorotation per-se, but...
With Autorotation disabled... If I turn my phone on its side (with volume buttons pointing towards floor) I still experience freezes on my home screen or anywhere else for that matter.
Plus I have found that holding the phone VERY still in any position seems to eliminate 'ALL' freezing and lagging problems.
Click to expand...
Click to collapse
Well ofc, it wouldn't freeze when it's COMPLETELY hold still, but I guess that shouldn't be the point of daily usage.
Now when it comes to spontaneous outside actions, you are trying to pick up a call using touchscreen cuz ur used to it or trying to shoot out a text in hurry, and your device will just go sleep for some time. I mean, how'd you hold still if you're moving (fast)?
If you ask me thats pretty much a major bug, not to forget the 3g data thing. I'm not moaning around, just want to attain more focus on this. I notice people losing themselves in some benchmark trolling - just time waste.
There is already a thread for that (walking dead)
Just found a possible solution, please repport if it is better for you too :
- boot windows mobile, calibrate the g-sensor in settings (i did it 2 or 3 times, but i don't think its important)
- do a proper shutdown of wm
- restart wm + android
Sent from my HTC HD2 using XDA App
After disabling "Auto-rotate screen" I haven't had a freeze yet, so good so far.