I recently upgraded to the Diamond 2 and I love the handset, but every other morning when wake up there is a msg saying opera performed a illegal operation and stopped working (or something similar ) or the battery has just run down during the night.
This morning I caught it just before it shut down, the power button switches the screen on and off, but nothing is updated (Time 0:12) And after reset the battery is a critical. I charged the handset at 15:00 yesterday.
Does anybody know if this is a known issue?
Well do you have turned Wifi or BT ON whole night?
What rom and radio are you using?
As I understand you left some programs in background running. Like opera. What else?
ROM version 2.17.421.1 (68613)
Radio 4.49.25.17
Opera never really closes. (want to use a cab file to disable it, but don't know if i should)
BT and WIFI not running.
I don't have any other applications running in the background that I am aware of. Haven't really installed anything. Except phone weaver. And GPS software
Well and how much power it has when You go to sleep?
If I charge at the morning I got battery sucked at the afternoon because I am using it as work tool.
But If I have 20% at the evening I got about 10% morning.
I use Energy Leo rom, radio same as You. At night I have only g-alarm in the background.
savagezaing said:
ROM version 2.17.421.1 (68613)
Radio 4.49.25.17
Opera never really closes. (want to use a cab file to disable it, but don't know if i should)
BT and WIFI not running.
I don't have any other applications running in the background that I am aware of. Haven't really installed anything. Except phone weaver. And GPS software
Click to expand...
Click to collapse
Stop Opera running in background:
Change:
HKLM\\Software\HTC\PushInternetEngine\Enable
1--->0
Use TD2 tools 3, go to Performance Tab, disable push internet. It will prevent Opera to activate, but also will stop updating internet pages if you have select these options. This will keep your battery alive longer also.
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.
nnnnnnnnnnnnnnnnnnnnnnnnnn
[email protected] said:
mattc 1.6 built with my hd2,Touchscreen freezes still exist.
and you?
Click to expand...
Click to collapse
READ THE FORUM RULES!. It's a known problem which has not been completely fixed yet. Dont just download and install. the same way developers take their time to make roms, you have to take the time to read. Read!
Shadow is right, the problem exists mainly in the kernel not the rom, but it's true that it's worst for some people.
happy to say that I have virtually no screen freezes! Here's what I did:
using setcpu overclock to 1152 and set it to interactive, then set on boot.
That's all.
If you still have problems, disable background sync. That did it for me in 1.5b.
I'm using ChuckyDroidRom 8/21 with radio 12.50.xx
Sent from my HTC HD2 using Mattc Froyo 1.6b
It is G-Sensor problem ,you can off the auto landscape function
cloud1027 said:
It is G-Sensor problem ,you can off the auto landscape function
Click to expand...
Click to collapse
This may be the case for some people, but I have turned it off and still get touch screen freezes...
Ive upgraded my android from matt 1.5b to matt 1.6b and no more freezes
Sent from my HTC HD2 using XDA App
its also related to the battery monitor, i get no screen freezes until my battery starts to get low, then the battery calibration goes off and i dont know how much power i have left, could say 27% but only have 3%
Fensy said:
This may be the case for some people, but I have turned it off and still get touch screen freezes...
Click to expand...
Click to collapse
Im useing shubCRAFT 1.4d ,it is no problem .
And than set display auto landscape offoff, and cm setting -> user interface -> 90 & 270 degree off
It affects me allot when playing games and screen freezes ,very annoying :S
Sent from my HTC HD2 using XDA App
No touch screen freeze.
My testing environment:
mattc's NexusLeo v1.0 + [email protected] #78 (r8) + turn off the auto-rotate screen
Hmm I think we just have to wait for a proper kernel, I mean autorotation is indispensable into the gallery or with some great games...
im still getting screen freeze with nearly every rom i try even though its not mentioned in the "not working" or notes parts at on the first page of the roms anymore, very annoying!
i am currently running
tytungs NexusHD2-Gingerbread V2.3
does anyone know if there is a way of keeping the gps alive when the screen goes off as i use my phone alot for tracking and the problem is at the minute as when the screen time outs so does the GPS
where as ideally i would like to keep the GPS alive once the screen is off
can anyone help?
I'd like to see that too, but i think it might be like the wifi a sleep policy, unfortunately I wouldnt even know where to begin to look, but since it exhibts the same thing as wifi did, I would think thats where the devs would need to look, but it could very well be a Google issue, but I'd love to hear someone who knows more then me.
I would also REALLY like to know how to keep the GPS on when the screen is off. Otherwise it really is useless for tracking.
WM6.5 used to do it no problem with RunGPS and other programs, but with Android (I'm using MDJ's Cyanogen 7 ROM) RunGPS and the awesome program Locus just can't be used for tracking for any considerable length of time if you have to leave the screen on since that causes massive battery drain and also random screen touches which open and close apps and mess with settings.
Do all of the Android ROMs for the HD2 have this issue?
From what I have tried it seems to be all gingerbread based builds, I have gone back to tytungs froyo build where tracking apps actually work
Sent from my HD2 using XDA App
My Acer works just fine for orientation sensor games, like asphalt, need for speed, etc. However, when I use things like ilighter, ibeer, etc the orientation is very off. The application is supposed to be help in portrait mode to be considered upright. However, when I want to use the program, I actually have to hold it in landscape (a 90 degree turn counter clockwise ) to actually have the program register that it is "upright". I originally thought that this was a problem with the program, but there are a number of programs that act this way. It acts this way regardless of orientation lock on/off or any settings, and only impacts on some applications.
Is this a common issue on the tablet device due to honeycomb issues, or is it something wrong with the sensor?
Anyone having similar issues?
Thanks in advance.
This is probably due to the different Android versions we use.
I have noticed the same issue on some apps that were made for my phone running Froyo (2.2). The app works fine on my phone and it reverses every sensor on my tablet so it becomes useless. The app you're trying to use is probably not made to support the tablet hence the sensor problems.
Ive been testing this out with other things. like bubble level, flight games, labrynth, etc. ever application is off. It seems to be seeing the x and y axises as being different. x=y y=x etc.
Anyone able to try downloading ilightr or ibeer or bubble or some other setup and seeing if they have the same issue or not, please?
phoenixbennu said:
It seems to be seeing the x and y axises as being different. x=y y=x etc.
Click to expand...
Click to collapse
exactly the same here...tested with ibeer, bubble, turbofly 3d.
i don't know if it's the same problem with a 3.1 version. i've tested all the apps with 3.2