Related
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
had this problem once: I switched on the camera, and then left the device on the table for a long time - so it went to standby.
I could not wake it up by the power button after 20 minutes, but as an incoming call came, it was ringing with a black display, and I could answer the call with my BT headset. screen was still pure black
finally I pushed the reset button and since then everything is fine - I still feel this was connected to the camera.
terta said:
had this problem once: I switched on the camera, and then left the device on the table for a long time - so it went to standby.
I could not wake it up by the power button after 20 minutes, but as an incoming call came, it was ringing with a black display, and I could answer the call with my BT headset. screen was still pure black
finally I pushed the reset button and since then everything is fine - I still feel this was connected to the camera.
Click to expand...
Click to collapse
Yeah if it only happened the once then that was probably the case, if you have the problem on a regular basis and you know its nothing to do with the camera (becuase you never loaded it) then you have the problem I am describing.
I have exactly the same problem has Terta.
I'm 100% sur that it's the camera that make this bug I have tried all my weekend to reproduce the bug a lot of time and it was always the camera...
Hope someone can fix this bug cause now I can't take any photo without soft-reseting my phone. Very, very, very annoying...
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Yes I guess there are many reasons for the Standby of Death, if you have ruled out all software causes such as the camera or installed apps then have a think about the SIM and/or the settings that impact the SIM.
Its the last thing most people will think about. It worked for me and got rid of a random SOD problem 2-3 times a week which coinceded with being in weak 3G areas (where the phone might switch bands automatically) although that never occured to me at the time.
You see I haven't installed other applications nor do I load up the camera and leave it running so I couldn't figure out what was causing it, it just happened randomly not connected with anything particular that I was doing.
i hope there is some kind of magical solution for this because i just got my Sprint TP2 today and I have this issue everytime my phone goes into standby. Pushing the power button wont bring it out but every once in a while opening the keyboard does. I have to continually reset my new phone just to use it
PS; beyond this annoyance, I love it!
coppertop24 said:
i hope there is some kind of magical solution for this because i just got my Sprint TP2 today and I have this issue everytime my phone goes into standby. Pushing the power button wont bring it out but every once in a while opening the keyboard does. I have to continually reset my new phone just to use it
PS; beyond this annoyance, I love it!
Click to expand...
Click to collapse
Try taking out the SIM card and see if it still happens everytime the phone goes into standby...
For the past few days I have been restarting my phone thru the soft reset. I think this is a windows issue...it has happened to me even without having the camera app running, and yes I checked the task manager. Hopefully this will be fixed when windows mobile 6.5 comes out, since Im getting frustrated with this phone...I have the phone for about a month now....grrr Stand by of Death!!!
coykiam said:
For the past few days I have been restarting my phone thru the soft reset. I think this is a windows issue...it has happened to me even without having the camera app running, and yes I checked the task manager. Hopefully this will be fixed when windows mobile 6.5 comes out, since Im getting frustrated with this phone...I have the phone for about a month now....grrr Stand by of Death!!!
Click to expand...
Click to collapse
so its not just mine then? this is ridiculous
Right, i had got seriously fed up with the standby of death happending, so i decided to contact HTC Europe directly.
They went over the usual 'factory reset' and 'update' solutions before coming to the conclusion that either there is a loose connection/faulty screen or there is some confiliction between drivers of the pre-installed software.
Because all HTC phones have 2 years warrenty as standard they have asked me to send if off so they can invistigate the problem and send me a replacement.
So if anybody is in the same boat as me a suggest you contact HTC and arrange a fix/replace.
Hope this helps.
nlel said:
Yeah if it only happened the once then that was probably the case, if you have the problem on a regular basis and you know its nothing to do with the camera (becuase you never loaded it) then you have the problem I am describing.
Click to expand...
Click to collapse
Add me to the list, seems to happen when I am charging my phone and it hits 100%
This phone reminds me of all my previous Sony Ericsson phones....very unstable OS' ... Makes me regret of getting this one and should've gotten an iPhone...but then again I'm pretty sure iPhone's have issues that apple fanboys aren't admitting. The reason that made me not get an iphone is because of ATT's ridiculous plan pricing...Its crazy!!!
if you are on sprints network, take out the sim card. This has fixed the issue for me. Used to get SOD a few times a day but opening the keyboard and then pressing the power button used to get me out of it. This was really annoying, and i read that it may be issues with the sim card. Took that out a week ago and havent had a SOD yet
jabberoo said:
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Click to expand...
Click to collapse
Jabberoo I can verify that this was caused by the SRS WOW HD program on my touch pro 2 as well. AS SOON as I uninstalled this application, restarted, everything was fine again.
I don't know if this will help anybody but if your phone suffers from SOD and you have TMO put it in airplane mode and see if it still does it.
I did that and it never went into SOD so that lead me to believe that the radio was the culprit. before that I tried everything listed. I don't have the 3G Plan so the 3.45.25.14 (T-Mobile) radio is the only one that worked for me.
I have the same problem.. just have installed spb mobile shell with mskip ultimate. I try to unistall all
I have a question: if I choose the 3G only option (WCDMA + UTMS 2100 in Europe) and the signal strength is low there will not be an automatic switch between 3G and 2G am I right? ...and i'm offline then
jabberoo said:
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Click to expand...
Click to collapse
sanjsrik said:
Jabberoo I can verify that this was caused by the SRS WOW HD program on my touch pro 2 as well. AS SOON as I uninstalled this application, restarted, everything was fine again.
Click to expand...
Click to collapse
Confirming this....
I had this issue for a while now...I tried hard resets, ROM flashes etc. It all works fine and was stable until I flash Sps Wow HD (I just realized this). Yesterday I flashed the latest HTC released sense ROM and right now after installing all the softwares I had the SOD again. Fortunately I saw the 2 posts and thought I will give it a try...and guess what?
I uninstalled the Srs Wow HD and phone is back to normal...no issues till now...will report later if I see any.
I am going to tmobile to get the SIM changed anyways hoping that it will fix another issue I am having. Every day I have to turn the airplane mode ON and OFF at least twice to get my data connection back. Mostly after a call and sometimes in random the phone is unable to reconnect to the data, it gives me an error that the epc.tmobile didnt respond or something like that. If any of you know how to fix this issue...plz help
I have been Experiencing this so called "SOD". HTC touch pro 2 sprint. On the 6.5.5 Build 23569 i had MAJOR sod issues. Energyrom , mighty , titanium , you name it. Ive Task 29 and reflashed them all multiple times. Still SOD was there... But i may have found a temp cure for me atleast. This is what i did....
First , i used task29 , next i reflashed the stock 6.1 rom, check for SOD... still had it... i task 29 again. Installed titanium edition , without sense. SOD was cured, phone worked fine, tryed to install sense 2.1, failed, SOD was back. Soo...
Then i task29 again, then repeated task29 a second time at the boot screen.... then i flashed Energyrom GTX themed 21907 build june 27th......Once it was flashed unplugged my USB plug and plugged it into the usb wall plug i have . Installed LUMOS, light sensor still was inactive and no response, could not brighten and still nothing... Installed G-light right after lumos without uninstalling lumos.... Still plugged into the AC wall USB plug....let it sit. Still nothing, couldnt adjust or brighten..... So i task 29 AGAIN... then flashed 21907 build GTX themed again... once flashed, unplugged it & back into wall charger... Installed lumos.... SUDDENLY!!! the sensor worked, and was accepting light AGAIN! ...
So i ran the LUMOS wizard, followed instructions and my phone was SOD FREE!! Let it sit over night, was fine....I wanted to see now if i could overwrite / flash over GTX themed with DiNiK glass cause i liked it better... so i DID NOT USE task29 this time, just reflashed over GTX themed one With DiNiK glass... same build 21907 and followed all my same steps, with wall plug, installed lumos, did the wizard,.... WALAaa.... works still like a charm. Have been using and testing it for 5 days, SOD is gone as far as i know.... ALSO in options, under setting / system / power / batt... i turned off the option to charge it when plugged into PC....Not sure if it helps or not. But Something i did is doing the trick. Seems between the backlight, and something to do with my 2.0 usb cord thats messing it up.
Seems to be cured... Still not sure exactly what fixed my phone. But between all that, IMO i believe installing lumos and glight triggered something also i think not letting it charge thru the PC, and only using a wall plug for charging has something to do with it....Either way . now its back to normal working just great... ONLY running LUMOS cab, and all the games i want. Energyrom Build 21907 DiNiK Glass Themed june 27th.... HOPE this helps!!! Have a wonderful DAY!
Hi,
I just got a new HTC Desire Z Bell Branded (A7275) for my AT&T service. I "debrand" it using the debrand guide. I just noticed twice yesterday that when I put it in standby mode, I try to press the power button to turn off standby mode so I can get the screen to slide down to unlock the screen for usage. Well, it did not....no matter what I do...I cannot get the screen to get unlock. The screen is black as if it isn't on. I hold the power button, still nothing. Only way is for me to pull the battery out, put it back in and power it up. Is this common? What is the problem that causes this? Any help would be nice. Thank you in advance.
have you oc your phone at all? have you flashed a kernel? custom rom? and what guide did you use?
I used this guide to debrand my phone.
have you oc your phone at all?
Not a single bit, everything is bone stock regarding CPU.
have you flashed a kernel? custom rom?
I only flashed the one from the guide.
[ROM] RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M
what guide did you use?
http://forum.xda-developers.com/showthread.php?t=835777
Thanks for the fast reply and help, bahmanxda.
Tbh I am not sure what is the problem I got nothing ,the only thing that I can think of is if you are already rooted and s/off do a full wipe and flash the Rom again or try different roms if u like sense try virtuous 9.0 its really good.
Sent from my HTC Vision using XDA App
There are some others with this issue. Unfortunately, the cause has not been found, or whether it is hardware or software related:
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
I've had this crop up myself a few times. I can say this:
Several times my Desire Z has powered off and could only be powered on after pulling the battery and re-installing. It did this twice within the first few days I owned it. Then it didn't happen anymore.
Maybe a week later I tried the Godspeed kernal (1 GHz) and SetCPU. No issues for about 2 weeks.
Then I tried CPU Tuner based on claims made by some users here that it is easier on battery life. Used a screen-off profile to underclock. The phone had the power off problem, 3 times in 2 days. Every time when the screen was off. But the random poweroffs did not start immediately after installing CPU Tuner, maybe 2 days later.
I uninstalled CPU Tuner to see if it would help (and it didn't seem to be improving battery life). Went back to Set CPU (have messed around with and without screen-off profiles). Its been more than 2 weeks, and no random power-offs.
None of this is conclusive, of course. Maybe the problem in my case was CPU Tuner, or a combination of the kernal and CPU Tuner. Maybe the things I've described are complete coincidence, and its some other factor altogether. But just thought I'd throw my experiences out there. Some claim Google Maps is the problem, but I have not found this to be the case. Or possibly some issue with the battery contacts, or the battery itself. Who knows?
Same thing happens to my Bell Desire Z. Every now and then it just decides to freeze and Only solution seems to be to take out the battery and then put it back.
Very frustrating.
Thanks for the reply, everyone. Strange it has not happen for the past 2 days now. I've read the other thread and still no exact detail on the cause of this. This is not good...especially it is my first Android phone and first HTC (bought it due to their reputation of quality made phones).
It happened twice within the first week of using the phone. Decided NOT to return the phone to observe it for a full month. During that month it happened every 3-4 days, always happens when the phone is not charging, and at the hour mark. Decided enough is enough and returned for a warranty claim 2 days ago.
During the one month, I rooted the phone after 2 weeks and flashed a custom ROM, but the problem did not go away.
There're people who aren't affected by this problem though.
I've the exact same problem here. CM 6.1.1 will just randomly black screen on standby. No response to charge when plugged in. The only way to reset is to pull the battery.
I don't think it happened on stock firmware. I'm now highly debating switching ROMs. It's getting annoying to remove the back cover every time I need to do a hard reset.
I think there is a thread in regards to CM and overclocking causing a screen on issue. But I think in those cases, the phone has power (LED and front buttons light up), just the screen can't power on. But adjusting any overclocking/underclocking profiles is worth a try.
Do you have SetCPU or CPU Tuner setup, and any profiles under those, such as underclock when the screen is off? I tried CPU Tuner for a few days, due to claims by XDA users of better battery life than SetCPU. I got 3 instances in 3 days of the phone not being able to power on (had to pull battery). I un-installed CPU Tuner, switched back to SetCPU, and haven't had the power on issue crop back up for almost a month now.
Given, I had the power on issue 2 times before using CPU Tuner, so it can't be the sole culprit. My only theory is that some combination of switching the kernel and SetCPU has solved the issue. Or it has nothing to do with those at all, just a coincidence, and is something else completely. Who knows.
It happened to me many time already. I still use stock htc desire rom and never rooted..
I've had it happen about 6 times, always requiring a battery pull. Totally stock other than being unlocked, not-rooted. But it hasn't happened for the last 3 weeks or ever since I stopped using juicedefender. Coincidence?
Desire Z freezes
Hi,
I also have some random freezes of my Stock Desire Z, I didn't do a thing on software or hardware side.
I run Android 2.2.1 Build 1.72.405.2 CL296256, provider KPN (Rabo Mobiel)
I got rid of the hangs after the upgrade from 2.2.0 then after several weeks it came back, only solvable by removing the battery.
I tried to figure out what's wrong and I think I have several clues:
- mostly some time after using Google Maps
- mostly when Wifi was on (it might be that the Wifi has limited connection and it screws up the data)
- after the reset I allways have updates from Market available
I can't remeber the Memory widget I ran, which I felt was having a good influence on the hangs.
I'm not happy with this behavioure, but cannot determine if it is hardware or software, it's not helping much that the phone just stalls , a reboot is irritating but less then a complete hangup when you don't know how long it has been in that status.
P.S. I don't run juicedefender
Cheers, Edward
I have STOCK G2 ROM.
S-off, CID, unlock via http://forum.xda-developers.com/showthread.php?t=855764
NO Cputuner or SetCpu (well I uninstalled them before these problems cropped up)
Used G2 for about a month and a bit no problems. Installed launcher pro then started to experience this problem. Coincidence? Not sure. Uninstalled and it did not help. Uninstalled several more apps that I recently loaded (skype, minimalistic text, Gtab Simi clock...) didn't help.
Wiped phone, nandroid backup to original ROM, restored using TB. Worked for a few days then just started happening again.
I also was using 2 chinese batteries I bought from eBay. Not sure if this has anything to do with it either.
// Just reflashed, HTC stock battery. Froze up within an hour. Too bad I bought this off of ebay, no warranty
// Factory Reset, restored apps and data with TB, still freezing
Hi all
I'm new to this forum (sorry, a newbie about to make a whole load of gaffs, no doubt), but I am at least fairly tech-savvy. I've had HTCs for years, right from the days of the 2000 vintage Compaq Ipaq!!
My wife & I bought two Desire Zs at Christmas, and it was therefore 50:50 which box was opened by whom. It appears I picked the dud, as I'm suffering from the issue described by all you guys, and in the other thread:
http://forum.xda-developers.com/showthread.php?t=857584
For the sake of adding more evidence to this otherwise confusing issue, I thought I'd join the forum:
So:
1) The device is not modded in any way. Standard ROM from HTC, being used on the UK T-mobile network. Currently at Android 2.2.1, Kernel 2.6.32.21-g540976a, Build 1.72.405.2 CL296256 "release-keys". This was installed on Christmas day, over the air.
2) There has been no playing with processor speeds or memory management.
3) The first crash of this nature was either on Christmas Day or Boxing day (ie the day-after-christmas-in-England); can't quite remember now, but certainly after the ROM update.
4) I have had this occur irregularly, but in increasing frequency, since that date. I think I'm probably into double figures by now, but I've only started to log them recently.
5) I was starting to think that there was some correllation with GPS applications. The phone would die after using Google Earth, for example, but not immediately. It may be after two or three standby's that it would fail to respond on the fourth, for example.
6) I had a very bad day a few weekends ago where the phone died four times in a single day. I had been using geotagging-photos (in the standard HTC camera app)... plus location-based services such as Yell and Google maps.
7) I tried keeping GPS disabled, and to be fair, there was no evidence of it crashing at that point. But I use GPS too much to make this plausible for a long time.
8) I wondered if it was due to the motion of keeping my phone in my pocket, but it died over night on the bed-side table on Monday-Tuesday, where my last usage had been the Friend-Stream widget/app. GPS was on...
During all of this, my wife's phone has not shown any of these symptoms. Whilst she uses Google Maps, Google Navigator & HTC Navigator a bit, she generally keeps the GPS turned off except for specific odd occasions. Hers has not crashed in this manner...
About to contact HTC to see what their response is...
This has occurred for me regardless of app usage.
It can occur right after a fresh reboot after being fully charged.
// Wow, I was in the middle of sending a txt and it just shut off on me...
I really wish I had a warranty on this
Hey there.
I can clearly pinpoint the problem with my desire z to the GPS. In the first view weeks I used it regularly and my phone froze, but only when the gps sensor was not active anymore (and the phone had gone to standby once or more). It didn't matter which app I used. For a while now I haven't been using GPS and my phone runs smooth as hell.
@lost800: I suppose your problem has a different kind of nature.
I already contacted HTC (very good support) and they told me to send it in to repair. I need my phone for work at the moment and I haven't found time to do this.
Due to the very small amount of ppl having that problem, I suppose it's an hardware error.
Greetz
Edit: Just out of curiosity, is there any meaning to the kernel version? Or has every mobile phone the same one?
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
dwardo said:
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
Click to expand...
Click to collapse
I called HTC support to see about getting the phone replaced. After explaining to the guy that it was freezing and then not rebooting when I pulled the battery out, the first thing he said was: "Did you install apps from the market ?"
Given that I replied by the affirmative he wanted me to test rebooting in safe mode and seeing if the freezes still occured before moving on to a replacement. He claimed that some market apps are not "properly coded and can mess up the phone"
I asked for and got the instructions how to reboot into "safe mode" (hit keyboard S key at HTC logo and stay on it while it boots)
In "safe mode" you can still install apps but they won't appear in the app drawer so you won't be able to start them (you can start them if they are on your home pages though ). No backgroud apps will run though (bbc, task killer ...)
Well I ran in safemode for 6 days and used the phone as I always do (work email, leisure email, web, video, camera, games, GPS, bluetooth etc...) and the darned thing ran perfectly. No freeze during those 6 days (the last few times it took less than 2 days to get a freeze).
I therefore decided it was time to test it again in "normal mode". Before rebooting I removed my task killer as for me this was "THE APP" that "safe mode" was really blocking from running on my phone...
Well It has been 2 days now and still no freeze. If it stays that way for another week I think I will have a rather good idea of who was the culprit...
Will keep you all updated and keep my fingers crossed.
Hi guys
An update:
HTC over the web-support were very helpful. Immediately they suggested that the device needed to be taken in for repair. In subsequent stages of the dialogue, they stated that the mainboard would be replaced.
A couple of weeks ago, I cleared down my device, packaged it up and waved goodbye to it (sniff...). HTC took it and...
!!DID NOTHING!!
It came back on Monday with an *old* ROM installed (1.35... If I remember correctly), and a statement saying 'no fault found'.
I've built the phone back up to where it used to be, including installing the over-the-air update to 1.72.405.2 (I need this as there's an activesync exchange bug in the old ROM) and within 24 hours, the device was unresponsive again
I have just written back to HTC to find out what the next steps are. I'd be interested to see if they suggest some debugging actions, like the safe-mode option, for example.
I've also asked them directly if their engineers have any clue what is causing this? Fundamentally, I don't see how any app should have the power to kill the device, however badly written it might be. That suggests insufficient controls/barriers in the OS.
Throughout this period, my wife's phone has continued to operate perfectly, even with some extra GPS playing to try to force a failure. So, we are now looking for any differences that could help to pin this down further. One difference is that she has never enabled the HTCSENSE.COM account on her phone, whereas I had. Perhaps there's some problem with the Phone Location functionality (in addition to the fact that I have to be in a yacht off the West coast of Africa for it to accurately show the phone's location). To test this, I've removed my HTCSENSE.COM account this morning.
Dwardo: I think your issue is slightly different, but the safe-mode info is useful.
Thanks
Andy
Hello all, First, I searched the forums for my answer with no such luck, that being said if Im repeating a question thats been asked I apologize. I have a problem with keeping android stable. I have flashed with different versions of windows several times all with success. I do however, prefer the android system, I find that it runs much better, faster and has better perks. Everytime I flash following the original how to, I run in to a couple similar problems.
The first is when I hit the power (not hold the power) the back light cuts off and the keyguard enables, the screen goes dark all as it should. Depending on the time ( the longer it is the worse it is) when I hit the power key to revive my phone, I often get a white screen, then it waits , then it goes dim, Sometimes If I hit the power button several times it eventually comes back to the key guard option, but others I have to remove the battery and reboot. This is the major problem, as I cant use my phone when I need it. This problem seems to get worse the farther it gets away from the flash date, e.g..,, after a brand new flash it works pretty good and then it goes downhill from there.
Second, it seems to lock up when I let it charge overnight, not always (but most of the time) I get up, click the power button to revive the phone and I have a white screen before me that is frozen solid. This like the previous problem seems to be linked to the distance from the last flash.
I hope that its something Im doing wrong, as Im currently using wmobile 6.5 and since Ive had a taste of the droid os, my wm phone is just disappointing. And as I was unsuccessful in finding a post that adequately describes my problem ,Im hoping that there is a way around this .
I have tried, Incubus Superfroyo, Wrym warm donut, and Cyanogens build. Im sure Ive tried others, they just escape me, I was re-flashing daily until I went back to windows. I truly hope someone out there has encountered what I have and has a solution. thank you all for what you do, these forums have been extremely valuable and helpful.
Sounds like you have the wrong panel type selected. Is it set to auto? if it is, try setting it to 2 instead. That cleared up the problem for me.
Tried all panels all have the same problem.
Well thanks for all the many replies. I give Ive tried everything on this site and m android is still really glitchy. Guess it will be windows until I get perhaps a phone capable of running android smoothly.
What kind of phone do you have?
Sent from my HTC Vision using XDA App
do you have an SD card you can try to boot from and share your settings?
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
I know, I know that MANY PEOPLE THINK OF THE WAKE UP WHITE JIBBERISH SCREEN as NEVER WORKING.
PoXFreak said:
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
Click to expand...
Click to collapse
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
srlebonv said:
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
Click to expand...
Click to collapse
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
You say that often install with data on the sd card causes lock ups and freezes. Can you explain further what you mean ?
dark_prince said:
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
Click to expand...
Click to collapse
Ok, so I installed your version of froyo, the accompanying 2.6.25, the radio that you use. For the most part the hanging up is fixed. Now the second problem is still in place. Sometimes when Its been in hibernation(or whatever you would call when you hit the power button once ) when I attempt to refresh my phone (hitting the power button once) nothing happens, the green light is still blinking at the top but the screen stays blank, normally have to remove the battery and restart to get back to using the phone. Is this a sleep setting? or is this something Ive done wrong during the installation.
Hi,
First post, feels like I'm a little late to the party. I have a gio which initially had gingerbread 2.3.3. The phone is unlocked, and rooted, and has the clock work mod recovery patch on it. I have tried a couple of different versions of gingerbread, and am now running ice cream sandwich: kernel 2.6.35-7-galaxyics, CyanogenMod version build 9-20120610-UNOFFICIAL-gio, build number IMM76L.
Firmware-wise, it's mostly good, but I'm having a couple of weird issues:
1. The screen goes black on me periodically, and won't come back without pushing the on/off button. This is happening every 30 to 60 seconds of use.
2. The wifi crashes, a lot. With the older gingerbread I would get the word "error" under wifi in settings, and couldn't turn it back on. I would enter *#*#526#*#* to bring it back, but every 5 minutes seems a little excessive.
With the newer ICS, I've noticed I can play on a wifi link all day long without issue, but as soon as I set the phone down for a couple of minutes, wifi stops working. If I go into settings, wifi is on, but there's no connection. If I turn wifi off and back on, it comes back to life.
I guess, I'm wondering if these indicate more of a hardware issue than a software issue. It's hard to ask for support from my carrier, given I'm using an unlocked phone bought from a 3rd party, and have no contract.
zapstrap said:
With the newer ICS, I've noticed I can play on a wifi link all day long without issue, but as soon as I set the phone down for a couple of minutes, wifi stops working. If I go into settings, wifi is on, but there's no connection. If I turn wifi off and back on, it's comes back to life
Click to expand...
Click to collapse
I got that problem to sometime ,
And welcome !
send from my galaxy gio with paranoidAndroid Rom
Errors that you describe has a lot of people
The team is now working on ICS AOSP so be patient wait a little meringue as soon
And yet you propose to install something else that any CM
In total there is this quite a bit
update
A couple of things I've noticed:
1. The resetting wifi problem does not happen when the phone is plugged into USB.
2. The screen turning off happens frequently, but about 1/2 of the time, the screen will turn off for 1-2 seconds, then come back on at full brightness; the rest of the time, it will not come back on at all, but still responds to being tapped. The only way to get it back is to push the on/off button on the side twice, but then the screen is locked, and has to be swiped to unlock.
I have picked up a second phone, a 5660M running stock gingerbread 2.3.4, unlocked and rooted; not experiencing either of the two above issues (and the camera preview works). If I could take the 5660 back to stock at this point, I would prefer that, as the phone is not usable with these problems. Is there a stock rom available for this phone somewhere?
update part II
Hmm, after the phone showed up with 2.3.3 claiming to be a gt-s5660, and was sold as such, I finally put 1 & 1 together. I checked under the battery, it's a gt-s5660m. That explains probably all of the problems I've been having. Pity there's no ICS build for the M version of the phone.
You can use cm9 ics on your M model, it only changes your device id to gt-s5660, just dont flash roms with ODIN except roms for the M model.
Flashing from recovery wont install a baseband, with ODIN it mostly does, so the only roms you cant flash are old roms that still need odin like gioprio.
Flashable .zips are fine, all of them
Sent from my GT-S5660 using xda premium
The wifi problem might be hardware, m8
I don't know, as my gio has some strange problems as well and I've had ICS, Adrenaline ROMs, everything, and the problems still persist. At least they're not really bad to handle in everyday use but still, they're annoying.
Go to wifi settings - advanced - sleep policy- never
Sent from my GT-S5660 using xda premium
update part III
Since going back to GINGERBREAD.MUGKG3 / 2.3.4 for the GT-S5660M, the wifi crashing and screen blanking behaviours have completely stopped. After two days of running, wifi has not shut-off unexpectedly even once, and the screen does not blank any more at all.
The gps works now; it was not before. It used to sit for up to an hour under a clear open sky, day or night, and never acquire a single satellite. Now it picks them up within 30-60 seconds, though a full lock does take a couple of minutes.
The phone previously always indicated it was roaming, and would frequently refuse to send texts or make calls. I would get full bars for signal strength, but no connectivity.
I even got hold of the fm radio app, which was not included with the M version of the 5660, and manually installed it (phone must be rooted, and file system must be mounted read/write). It works too; a nice bonus.
The camera works, but is a bit flaky, requiring an occasional restart to get it going.
Probably the biggest headache, after flashing back to the 5660M version, was that the phone locked itself again, and wouldn't work on my network. I dumped bml5 page and searched out the unlock code. I had some trouble with this. The search string to get close to the code is supposed to be a sequence of twenty 0x00 bytes, one 0x05 byte, and fourteen 0xff bytes. The 0xff bytes weren't there, and it took a while for me to clue in that if I searched on the twenty 0x00, and single 0x05 byte sequence, I could still pull it out. I got it, and wrote it down in case this happens again.
sms issue
Still ticking along with the GT-S5660M; mostly it's all working nicely. I have one question though: I recently ran out of memory for storing SMS messages. It looks like the texting app in the phone wants to put everything on the SIM card rather than on the SD card, but there's no option for moving the default storage location for messages. Is there a simple way to do this? The phone is unlocked & rooted, but does not have the ext2 file system on it.
What's the IC? I checked under the battery to confirm mine is a Canada model, and it is.
But my IC is GT-S5660L
Model: GT-S5660M
IC: GT-S5660L
buremily You
Peteragent5 said:
What's the IC? I checked under the battery to confirm mine is a Canada model, and it is.
But my IC is GT-S5660L
Model: GT-S5660M
IC: GT-S5660L
Click to expand...
Click to collapse
Same, GTS5660L ... why do you ask?
Hey all,
So I'm posting this thread regarding a couple pretty weird glitches and bugs occurring on my G3, 3 specific ones.
The first: (Probably the least serious but still REALLY annoying) At EXACTLY 12:00AM every night no matter what timezone I set the phone to (I'm in AU on the AEST GMT+10 timezone but it does this at the same time on any timezone) the phone will switch it's WiFi off automatically without warning, reason or explanation. It just goes off and then I have to manually turn it back on. Sure I could use an app such as Tasker or AutomateIt to turn it back on but I don't see why this is occurring in the first place?
The second issue (Most recent): Lately after updating to the V20E firmware for my D855 I've noticed that a graphical glitch (Specifically related to the colour Blue) occurs when there are fast moving elements on my phone's screen (Such as when I move a chat head around on my phone from Messenger, or when I'm scrolling Facebook or my App Drawer fast, there's just a blue box around whatever object/s appear to be moving on my phone's screen. I've not dropped the phone at all, and it has only been present since updating from the V20D ROM. Not sure what could be causing it.
The third and by far the MOST ANNOYING of the issues I'm having, is that for no apparent reason, whenever I am listening to Music with the stock Music player, and I lock the screen (The screen goes off) about 5 seconds later weird stuff starts to happen..
The song will pause, play or even stop completely, seemingly on its own. The "phone" will change songs, artists and sometimes complete albums and playlists completely by itself, with me doing nothing but staring at the lock screen (It keeps doing it until I re-enter the Music app, then when I lock the phone the whole cycle just repeats itself.)
I've done some looking around and careful observations on the phone itself, and it seems that before the weird stuff starts happening to my music, the phone opens Voice Mate by itself, and then if I'm not present, it apparently closes it and then that's when the stuff happens. I've tried everything I can on a non-rooted phone to stop this. I've tried re-installing the Music app, Uninstalling all updates to the Voice Mate and it's packages to the factory version, force-stopping Voice Mate, everything and no matter what I do the phone still opens Voice Mate and the weird stuff starts happening (It's like it's taking commands from Voice Mate to do something but I'm not even doing anything ) It's been doing this since I got my phone when it came with Android KitKat 4.4 (I was on the D10M ROM until I moved to the D20D Android L ROM) and I moved ROMs doing a completely fresh start ( I factory wiped the phone and then upgraded via a CSE flash and put all my stuff back on it manually) and I would've thought a completely fresh start would have fixed it but apparently not... Either it's a bug that's been present for a while, or it's something deeper than the ROM.
So yeah some pretty weird issues, if someone knows what could be causing them, please let me know, especially if you know a way to solve them.
Cheers guys.
I'm having a very similar problem with regards to #1 but it's doing it with Bluetooth for me!
At midnight on the dot, it will disconnect my connected Bluetooth devices. It doesn't shut Bluetooth off, it just drops the connection. I posted about it here: http://forum.xda-developers.com/verizon-lg-g3/help/bluetooth-disconnects-midnight-t2973187
Your phone sound possessed! Call 1-800-Exorcism now.
You right, weird/unusual.