Related
HI,with respect to user's , admins n DEvelopers i would like to say SOD might be due to the sleep time settings (image attached)in brightness.i might be wrong or might not be,if im wrong sorry in advance n would req. the admins to delete this thread,Tnx to all..
EDIT :
Use mattcfroyo 1.4 (with latest cotulla zimage) or DARKSTONE froyo v1 latest(384ram enabled)
[my preference] with windows rom: chuky gtx/chukydroid/miri17.6
and radio 2.10.50/2.12.50 no echo no robovoice no sleep of death evrything is fine
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Stoferr said:
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Click to expand...
Click to collapse
thats y i let this info to other users let see what happens to them,n i dont hav n SOD problem but i have robotic voice :"S too bad cant get rid off it,can u sggest me a ROM,m using updated tmous ROM n radio 2.12.50.xxx.. tnx in advance.. and lets see what others say with sleep turned of.. and please do share your results... thank u..
Im testing it right now, so far no problems, but it seems randomly whener SOD appears, so i'll just test it a little longer.
Im using the european HD2.
hmm.. Lets see the results of other users also... and please do share ur findings...
P.S: m using TMOUS HD2 and waitin when i can get rid of robotic voice.
Damnit just got it! Well, seems that this won't help It was a nice try tho
i have never had sleep of death its gta be rom and radio related
i tried to help all... thats all.. but tnx for tryin... but i dont hav SOD either.. now dloadin maatcleo+froyo v1.2 n gonna test if it has SOD..
robotic voice is killing me :'(
I've had sleep of death with basically every android build out there.. i don't think it's a setting in my personal opinion. i think it is because it's still in develoupment and the drivers aren't 100% yet.. and i'm sure in time it will be fixed.
I tried it on zimage 7/25 and still have SOD .Some claim they use the new zimage without SOD ,no matter what I do it won't wake up.
the battery is horrible on 7/23 zimage and carrying the charger in my pocket all the time is a pain.
Off topic: I loved the notes on dna u had there
The "Turn screen off" setting is active in my WM. Using German T-Mobile 1.72 ROM, Radio 2.10.50.19_2, Dan's Froyo V1, zImage 25/7.
Using this combination for two days now and didn't have a single SOD during this time... only two or three times a freeze for few seconds, but afterwards Android resumed working.
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Been using dans13 build with cotullas no speddy zimage. My Rom right now MIRI 17.6 and Radio 2.12.50.26. No SOD report here just couple of freezes now and then. Good battery life. I have to say that I disabled the Auto lock in Windows with HD2 tweak. The first time I tried android on hd 2 i got the SOD, but with this combination and disabling the auto lock been running smoothly. just my 2 cents.
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
Well what I don't get is when I started trying Android on my tmo hd2 I didn't get the sod but now I do. if its the screen why did it start now?
Daaaaaaaaaaaaaaaaaaaamn waiting for new zImage... Seems that I have a sharp panel... How can I check this?
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
well now im using miri's v17.6 rom wid radio 2.12 on tmous HD2 no SOD till now although sleep is active in WM...
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
I've read the same but i think a lot of it is just down to individual ROMs & radio builds, as when android started on hd2 everyone said turn off backlight but mine was never on high nor did i alter any settings as when haret kicks in it turns off all windows functions altogether so you can't have any cross network/OS issues, winmo is supposed to be cut off. although saying that if android is only running off sd how can you remove sd and still run android for 1hr or more? but that's a different topic.
If you have a Tmo US HD2 just use Cotulla's 7/23 zimage and you should not get sod. If you use 7/25 zimage, you WILL experience sod! If you experience sod with 7/23 zimage, then the likely culprit is your sd card. Reformat and try again. If that doesn't work, you need to try a different card.
I am using the 7/23 with chucky's rom, and i was fine all day yesterday but this morning i got 4 sod in 15 minutes, and everytime i rebooted after that. I changed my Radio to 2.12.50.02 and i turned off the sleep thing in WM, and so far haven't had a sod in about 3 hours.
I was wondering if anyone else has experienced a problem with android on the hd2 where very occasionally on waking the screen up the colours become inverted? I couldn't find anything on the forums about it and it doesn't go away unless u reboot. U can still use the phone completely fine, it just makes things difficult to read.
I don't remember having the same problem in winmo which makes me think it's linked to android as I've only been running it on my handset for about a month.
I am using the cyanogen 6 android froyo rom with chucky's Droid rom for win and radio v2.10 (just in case that makes a difference!)
Next time it happens I'll try to get a screenshot too!
Any help/ideas on how to fix it would be much appreciated!
Pav
Sent from my HTC HD2 using XDA App
I also had that problem before, happened to me about 3 times with shu8i's previous build. But when you take a screenshot of, the screen shot is fine. CM6 related I guess but dont have clue. I just reboot
Same as above, couple of times on shui8, not a real pain, just rebooted.
Sent from my HTC HD2 using XDA App
Occured to me once on a sense build on Energy WM ROM.
Had to reboot to fix it
hmm guess its not necessarily android related then, and if the screenshot's coming out fine could even be the hardware! just seems to be happening to mine more recently, however since putting this post up it hasn't happened (of course!)
Cheers for the help guys, like you said its just an annoyance more than anything, just hope it doesnt get worse
Pav
I've had it once in FroyoStone V1, rebooted and then everything was fine.
inverted screen
hi guys, i've also experienced this problem, I was running at the Feather HD rev.3 at the time (great build BTW), and had this problem two times. As far as I am concerned I used my phone as usually ,so there is no root of this problem I am aware of. Obviously it is not even build related. I also attach screenshot.
I got the same inversion 4 times now with FroYo 4.6.
1/2 year with WiMo I didn't got it.
First I thought this occurs when unplug the power cord
but 1 hours ago I got an inversion just going from standby
to work.
This happened to me only once, while using sense ui, locking the screen and waking it. Rafdroid Desire HD Rom - MDJ Kernel
Can someone merge the thread with this one? http://forum.xda-developers.com/showthread.php?p=11161353#post11161353
same inversion
Hi, I have the same problem till reflashing to android, now I have MIUI and it happens approx. every 2nd day od use. Do somebody have any advice to this yet? Maybe it's related to version of RadioROM...?
Hi
I know, was discussed so many times...but because of just this, I'm confused as hell. Whenever my batterycharge is quite low, my phone starts to hang pretty frequently...the touchinputs at least. I noticed, that this happens, when I walked a bit with my phone. So my guess would be, that the g-sensor is overloaded and that freezes the touchscreen. I know, there are Kernels that deactivate the g-sensor, but it's a handy tool for screenorientation. So, is there a fixed kernel which leaves the g-sensor activated but removes the touchscreen-freeze bugs?
Hope someone can help me.
Greetings
NessD
wow ... i didnt know the battery charge has play in this ... i guess ill keep it better beefed up ... thanks for da tip
Its still a mystery to me. Because a lot of people seems not having this issue anymore.... Not me, with the last radio, trying wm roms and several builds. Like you, it is very hard to walk typing a sms. Ok I will not be hit by a car but its still frustrating hehe
Yeah, I just noticed that I get those problems when 2 cases are given: Low Battery Charge (full battery is no problem) AND when the HD2 moves around alot. I get touchscreen freezes then. Either one for it's own is no problem, but both keep producing the freezes.
I haven't had ANY touchscreen freezes using hastarin R8. It's actually probably the best one ive used. No touch screen freezes and the auto brightness works on CM6.
No kernels have fixed this yet, some builds claim "no g-sensor freezes" but they do. (or at least they do for me, i'm not doing something wrong am i?)
mmduluth said:
I haven't had ANY touchscreen freezes using hastarin R8. It's actually probably the best one ive used. No touch screen freezes and the auto brightness works on CM6.
Click to expand...
Click to collapse
Hastarin r8 does not work for me...using Hyperdroid v1.7, can't get data to work...
Experimental kernel released that (should) fix this.
http://forum.xda-developers.com/showpost.php?p=9194473&postcount=140
I can confirm it finally works. Today is a great day for the community
have you got the same problem?
the screen loses colors and get like white - but you still see the android theme, but in extreme white/pink-ish theme.
how to fix that, exept turning on and off the phone? and why does it do like that?
I have the same problem, buy it happens from time to time
im using radio 2.10.xx, witch ver do you use?
Same here.Radio 2.15,using NexusHD2 V1.9G.
Every couple of weeks.
Android in general is like that for us. Remember android wasn't "meant" for our device so there are still some things to work out.
Just restart your HD2s.
also got it from time to time...
it happened when the screen turn off and on too fast.
the only way to bring the color back is a reboot.
exactly the same to me....what's happening?
i use on hd2 the 2.2 froyo nand rom
Ive had (and posted) about this issue in past, its happened only about3-4 times to me so nothing really for me to get worries about. Just curious on what actually causes it and is it a sign of anything other then a driver/software failure?
got this problem ,too. but it started on my device with winmo6.5 cwf´s. i dont think, its a problem with android. iam on radio 2.10...
Same here ... more frequently though ... maybe once or twice a day.
Android HyperDroid GBX v11
Like a previous poster said this happens for me when the screen is turned off and on very quickly, especially while in a call. I think, for a moment, proximity sensor tries to turn on the screen and then off again.
Leo 512 only ?
Yes, system too big or big ! get other build
Me to had this problem using MIUI rom
Decided to do a full phone erase and SD format.
Seems to have fixed it
hi all
i have been using nand android builds since day one , and in most of the builds i am having this same issue
sometimes when i receive a phone call the system just hangsout and then gives me a force close msg for the phone application !!
either way , if i force close or not , no further phone calls can be answered and the phone will freeze for about 30 seconds with every call
also when this happens the volume buttons wont modify the volume for the media anymore and the phone wont give any sounds
so is there something i can do to get rid of this ?
i tried android builds based on 2.3.3 and 2.3.4 , miui , sense , no sense , and i have this issue with all of them
again , it happens like 10% of the times
hope i get an answer to this
I want to ask what exactly rom are you using (does it use newest tytung r10 kernel?) and tell you that I have not been experiencing these issues with NexusHD2 2.8 rom (2.3.4).
fpu
i tried typhoon , rafdroid , ndt miui , and plenty more and i think typhoon and ndt miui has the latest kernel
have you ever tried receiving a phone call while the camera application is running
this seems to trigger the issue many times , not always tho
if you have the call recorder running turn it off. it was causing me lot's of problems.
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
domenukk said:
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
Click to expand...
Click to collapse
+1 Same ****...
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
I just recieved a phonecall without problems.
Flashed the .12 radio from http://forum.xda-developers.com/showthread.php?t=611787&highlight=radio
however... My rom feels a bit slower now.
I am playing with it now.
Maybe clearing Dalvik cache will help. Or the issue comes back... Will see.
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Synthezys said:
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Click to expand...
Click to collapse
Switching Radio to something.12 did the trick for me.
No problems for two days now.
domenukk said:
Switching Radio to something.12 did the trick for me.
No problems for two days now.
Click to expand...
Click to collapse
Leo_RADIO_2.12.50.02_2 - is this good?
Synthezys said:
Leo_RADIO_2.12.50.02_2 - is this good?
Click to expand...
Click to collapse
Yes that's it. Works fine for me
Mea culpa just today I had the same issue, for first time.
It's nothing major and reboot made it work fine again, but breaks my belief in HD2 as perfect, native-like Android device.
[email protected] said:
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
Click to expand...
Click to collapse
Beside changing of radio, THIS seems to be interesting.
I'm on MAG but considering switching to cLK (for many reasons - fastboot support being one, second that I don't need 99% of MAGLDR features).
Let's see how it all pans out ;-)
fpu
It just happened again! On the new rom... :/
There is a thread, however, stating that it's due to skype.
This can very well be true.
http://forum.xda-developers.com/showthread.php?t=1164058
but I need skype to stay on contact with my girlfriend... why can't android support skype natively instead of sipthings? -.-
Well still... anyone tried clk (instead of magldr) and skype?
Disable "Audible touch tones". It's under Sound in Settings, it did the trick for me.
I thought this was against robot voice?
well what ever. let's give it a try. Thx
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
An0n1mUs said:
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
Click to expand...
Click to collapse
For me recieving a call does nothing but a very bad noise. hd2 nearly freezes after that. I cannot hang up most of the times. If I somehow manage to, phone app forcecloses and connection cannot be reestablished until I pull out the battery...
Good old Robotvoice. I wish that was my problem.
i have switched to cLK about 3 days ago and till now i have got no problems at all