I've read lots of comments, these very unwanted random hard-resets are suppose to be a common bug, however the suggested fixes dont seem to work for me, anyone else having the same issue?
Note: The issue must be software related, it only started happening to me immediately after a ROM update a few months back.
What usually happens:
- Install a ROM -> Configure It -> Install Apps... all looks good
- At some random point (could be days or weeks) the phone will lock up (usually on the password screen)
- A soft reset is required to rectify the lock-up
(i.e. the red button on back of phone)
- Phone hard-resets itself
Suggested Solutions:
1) Upgrade to HardSPL 1.93 - made no difference
2) I have tried running MTTY a few times, also no difference
3) Try different ROM's, I thought it might be just a bug with the WWE ROM, but it happens with the Energy ROM too
Just out of interest:
Interestingly, my wifes phone, which I do exactly the same updates on (same phone, same ROM, same Radio, etc), is working completely fine...
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
businello2000 said:
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
Click to expand...
Click to collapse
Hi, thanks for suggestion, although yep I tried that too. There is no stock ROM for an imported phone on Optus, but I just used the stock Telstra one that was on the forums, then after a while went back to the WWE ROM, and the same issue still occurs.
No other ideas for resolving the hard reset issues?
Next time it happens, I might try pulling the battery out instead of using the reset button on the back of the phone.. but clearly something is wrong :-/
i have had this a couple of times, about 6 months ago and last week. i just flashed a different ROM, flashing the same one again didnt help, so just downloaded a different one and went with that.
seems to be ok now
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
matrix77 said:
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
Click to expand...
Click to collapse
Thanks again for suggestions so far, but above fix only lasted about 5 days before another intermittent phone crash & subsequent hard reset, much the same as I have had experimenting with a range of stock and other ROM's :-/
I don't think the fix is as simple as just putting a Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset. Im pretty sure its a software problem, but I dont see how the problem can survive such rigorous formatting...
Is noone else having the problem? Sounds like most are solved with 1 use of MTTY.
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
The only solution is:
1st MTTY and run task 29 to format the device to make it clean and no left over stuff from the last ROM.
2nd Install different ROM
If you have bad sectors in the device, MTTY might not help much here, I guess.
Hi maddie, yes you might be onto something, I assume you already tried the usual fixes: (Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset)? You can tell it to format the NaviNAND during the hard reset.
I think my issue might be different to yours though, as mine does not happen 'when installing software' mine happens days/weeks after setting up the phone.. It usually goes down like this: I pull the phone out of my pocket -> its locked on the password screen usually (cant type) -> pull the battery out or press the soft-reset button -> bang.. phone hard-resets.
I will make 1 suggestion though, instead of using all the nice fancy mods, and SPB Mobile Shell (looks like sense ui), I went back to a boring old stock rom, and well after 1 month its still going.. I absolutely hate it, but I dont want to buy another phone quite yet, so gonna go old-skool.
Let me know how you go, and as above if you did all the standard suggestions? It sounds like you need to somehow instruct the phone not to use those bad memory spots, but ive no idea if such a tool exists im afraid.
maddie said:
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
Click to expand...
Click to collapse
I got the same problem recently and I am still trying different way to solve it.
My Hard-reset happen:
After flashing new rom -> Installation of software ->
-> launching programs -> when some got may holding or loading without response
-> Soft-reset (red bottom) -> It automatically Hard-reset....
Similar thinking with you, I think that maybe one of those reasons leading the hard reset:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
kenleekwanho said:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
Click to expand...
Click to collapse
I like this logic, im in the position of owning 2 HTC Diamonds with identical ROM, Radio, Applications, 1 works perfectly, 1 is resetting.
It 'probably' indicates that its hardware related, I doubt its Radio (due to the other phone working fine), so could be Internal Storage or Bad Sector.
Im not even close to filling up my internal storage though, so if its storage related, perhaps a particular sector is the problem (like maddie was mentioning).
Thanks for all your opinions!
It's the first time for me to think it's the Radio's problem. It comes to me now it seems this situation starts when I flashed the 1.15.25.14 radio. I will try another radio and update here.
I dont 'think' its Radio, but worth a shot.
I cant consistently reproduce my issue, so it could take me a month to find out if ive fixed the issue.. and there are a lot of variables in a month. But sounds like you have a way of reproducing it consistently, gl.
OK, it doesn't seem to work. I think that's it..
Maybe I should start looking at the bootloader commands..
ive got the same issue, but only with some ROMs, for example, the AZTOR X3 and GEN.Y D2 didnt work, but gen.y 1.4 worked for me.
I tried MTTY method to re-flashing, it seems fine to my diamond right now.
i have the same problem, i have tried about 10 different roms, but i don't think it's software related, i think it might be the phone overheating causing a faulty component, it started 2 days ago for me and usually after 5-10 min it crashes, and it started happening when the weather heated up and it will crash quicker if i try to charge it, anyone notice this?
Has anyone found a solution to this?
For me it started when I installed the Gen Y rom with the android dual booter (but not android itself). I have tried MTTY, Stock ROM but Im still experiencing the problem. I suspect it has something to do with the dual boot.
I get the same thing. soft reset = hard reset.
I have tried several ROMs but now the phone hangs on the loading screen
Related
any time now on any rom, i'll soft reset my phone and all of a sudden it goes to the windows mobile start screen with the screen calibration.. (basically a hard reset to a clean os)
how do i fix this, i been trying to find a solution to this problem for some time now but haven't got a concrete find for it
ezsoulja said:
any time now on any rom, i'll soft reset my phone and all of a sudden it goes to the windows mobile start screen with the screen calibration.. (basically a hard reset to a clean os)
how do i fix this, i been trying to find a solution to this problem for some time now but haven't got a concrete find for it
Click to expand...
Click to collapse
I am sure I have advised this when you wrote on one of the threads. Try flashing a shipped rom first, it is in my 4shared, doesn't matter if you have AT&T 8525 or not as it works for my jasjam. Flashing too many radios may kill your phone. So ... flash that and then flash the one you want ..
I have not in my time flashing my phone and my customer's phone that a soft reset causes a hard reset after following the doctors instructions
i will try that but what does the regular att rom have that customs dont to stop this from occuring
ezsoulja said:
i will try that but what does the regular att rom have that customs dont to stop this from occuring
Click to expand...
Click to collapse
As I mentioned no issues for me yet touch wood/knock on wood as your part of the world probably accustom to.
ok so far so good, no more hard resets but i just wondered what the original att stripped rom is actually doing to stop this from happening and how much more to reflashing the roms before it happens again..
it has something to do with the big storage/non big storage flashings etc and that shipped rom sorta resets it all to an acceptable state to the phone's brain so to speak .. the doc's never wrong
ezsoulja said:
ok so far so good, no more hard resets but i just wondered what the original att stripped rom is actually doing to stop this from happening and how much more to reflashing the roms before it happens again..
Click to expand...
Click to collapse
In a normal rom, the flash rom is split into two pices, ext rom and storage rom.
In a bigstorage rom, this boundery is removed.
Now, over time, this causes instability in the way windows access and manages the rom, leading to data loss (random hard resets).
Flashing a OEM rom with a OS partition and a Ext rom parition acts as a spring clean on the memmory layout, thus, stability.
As with windows, most things are solved by formating your HDD and starting again, its the same kinda thing!
Great.. Thanks guys, im back to normal now with no hard resetting.
my GSM module has something wrong,i think.when i flash 6.0.it was failed.when i flash 6.1 which without radio.nbh. it was successful.and then,first time boot up.sys must be reboot.OK,reboot.it stop in the secondsplash.it can connect pc with the activesync.but the phone screen is the secondsplash....i dont know why...pleaes help me..
thanks~~
I'm having almost the same problem. When booting, my phone gets stuck at the second splash screen every time. I tried reflashing numerous different ROMs, but I get the same problem every time. Occasionally, with a Dopod factory ROM, I get it to boot to the "no SIM" menu in Chinese, but after tapping through the menus, it just restarts and gets stuck at the 2nd splash screen. I searched all over the internet for various radio ROMs, but I can't find ones specific for the Cavalier. I tried some for different HTC WM6 phones, but it stops at 7% and tells me that the ROM isn't right for the device. I'd like to try a new radio ROM if I can, so if anybody has one, can you post it???
ttknf said:
I'm having almost the same problem. When booting, my phone gets stuck at the second splash screen every time. I tried reflashing numerous different ROMs, but I get the same problem every time. Occasionally, with a Dopod factory ROM, I get it to boot to the "no SIM" menu in Chinese, but after tapping through the menus, it just restarts and gets stuck at the 2nd splash screen. I searched all over the internet for various radio ROMs, but I can't find ones specific for the Cavalier. I tried some for different HTC WM6 phones, but it stops at 7% and tells me that the ROM isn't right for the device. I'd like to try a new radio ROM if I can, so if anybody has one, can you post it???
Click to expand...
Click to collapse
I don't think this has to do with the radio. From my experience in testing out cooked ROMS and trying to cookm my own ROMS for the Cav, the filesystem is a bit temperamental with too many flashes. I have had to format my ROM filesystem half a dozen times to fix small glitches such as incomolete flashes and hard locks. I can throw together a radio ONLY update for you but I doubt it will fix anything. This post describes how to unbrick (or format you phone) but you will lose ALL of your data and do it at your own risk.
http://forum.xda-developers.com/showthread.php?t=428589&highlight=brick
ookba said:
I don't think this has to do with the radio. From my experience in testing out cooked ROMS and trying to cookm my own ROMS for the Cav, the filesystem is a bit temperamental with too many flashes. I have had to format my ROM filesystem half a dozen times to fix small glitches such as incomolete flashes and hard locks. I can throw together a radio ONLY update for you but I doubt it will fix anything. This post describes how to unbrick (or format you phone) but you will lose ALL of your data and do it at your own risk.
http://forum.xda-developers.com/showthread.php?t=428589&highlight=brick
Click to expand...
Click to collapse
I've already followed this process with MTTY numerous times, it had no effect. Also, when I did info 8 and task 2a, there were no bad blocks to begin with. Is there something else that can be done w/MTTY to fix things? It'd be great if you could dump that radio.nbh onto this thread just to see if that'll fix things.
ttknf said:
I've already followed this process with MTTY numerous times, it had no effect. Also, when I did info 8 and task 2a, there were no bad blocks to begin with. Is there something else that can be done w/MTTY to fix things? It'd be great if you could dump that radio.nbh onto this thread just to see if that'll fix things.
Click to expand...
Click to collapse
Here is the Radio (05_GSM.nb) in the nbh. It's the one from the Dopod shipped ROM but I checked the versions and the HTC one is the same version. Copy this nbh file to your ROM Update folder and flash away. Hard SPL is recommended. This is a straight radio dump and I am not responsible if you brick your phone.
Haven't uploaded yet, will upload shortly.
ookba said:
Here is the Radio (05_GSM.nb) in the nbh. It's the one from the Dopod shipped ROM but I checked the versions and the HTC one is the same version. Copy this nbh file to your ROM Update folder and flash away. Hard SPL is recommended. This is a straight radio dump and I am not responsible if you brick your phone.
Haven't uploaded yet, will upload shortly.
Click to expand...
Click to collapse
Are you gonna upload that radio rom?
Hello!
Ive got a problem aftter flashing a *.nbh for NAND android :/ It just hanged on the splash screen. No any linux logs
If you can still get bootloader, try reflashing, sometimes it fails for no apparent reason, if that still does not work, try formatting the SD, recopy the nbh, reflash again.
If all else fails, you may be one of those who cannot flash to nand, I have 2 kais130's one flashes every time, the other, about 1 in 15 times is successful.
zenity said:
If you can still get bootloader, try reflashing, sometimes it fails for no apparent reason, if that still does not work, try formatting the SD, recopy the nbh, reflash again.
If all else fails, you may be one of those who cannot flash to nand, I have 2 kais130's one flashes every time, the other, about 1 in 15 times is successful.
Click to expand...
Click to collapse
I can still get bootloader, a reflashed, today i putted new SDHC card and i try to reflash nbh. Only 1 time after flash I can see linux logs, I can to install it too, but when ill reboot phone then hangs like early :/
Ok first which Android build are you trying?
When you say reboot, are you using the reset button or pulling the battery after flashing, ( using reset can cause problems, the correct method is flash, pull battery, wait, replace battery ).
Which nbh are you trying to flash? If you had android working then you may want to go back to the nbh you used before.
zenity said:
Ok first which Android build are you trying?
When you say reboot, are you using the reset button or pulling the battery after flashing, ( using reset can cause problems, the correct method is flash, pull battery, wait, replace battery ).
Which nbh are you trying to flash? If you had android working then you may want to go back to the nbh you used before.
Click to expand...
Click to collapse
Im using kaisimg-panel1-428-12-03-10, im using a reset button not battery trick. Im using warm donut biuld. As I said i can boot android from NAND just 1 time, not anymore
Well the best nbh's for the kaiser are still the sourceforge ones at least for stability, the 20/02/2010 ones, yes there are newer ones, but they may require some pretty advanced editing of some system files before they run properly, and may not be fully compatible with the donut build.
I think it may be better to use one of these : http://sourceforge.net/projects/androidhtc/files/2010-02-20/kaisereclair/
I have the same issue with dzos latest. I posted it in the bluetooth thread as to not open any unneeded topics. The fix he posted 11-03-10 for bluetooth booted fine, this one gives me the same issue. Remember this stuff is all relatively experimental so try not to panic when using the very latest since it might not work.
Apparently there is a problem with the latest nbh's, I'd just reflash an earlier NBH, this should fix the problem.
I'm having the exact same problem. Everything seems to get installed properly but once I take out the battery to reboot it just hangs on the splash screen. I've tried several builds and reformatted the card several times... always the same result. In one of the posts I cam across it was mentioned that you first have to go in to win mobile to turn off a pin # and that can cause the system to hang if not done. I can't find the post anymore and I'm not sure what they were talking about.
kcbronc said:
I'm having the exact same problem. Everything seems to get installed properly but once I take out the battery to reboot it just hangs on the splash screen. I've tried several builds and reformatted the card several times... always the same result. In one of the posts I cam across it was mentioned that you first have to go in to win mobile to turn off a pin # and that can cause the system to hang if not done. I can't find the post anymore and I'm not sure what they were talking about.
Click to expand...
Click to collapse
Yeah I read about disabling the pin thing in Win Mo as well, but unfortunately this was after I flashed Android to NAND. Mine hangs at the splash screen as well, but if you put the KAISDIAG.nbh file in the root of your SD card, from the Hard SPL threads, the phone will boot and get to the Android installer, but will then come up with errors when choosing to install to NAND. Unfortunately, I can't even go back to Win Mo because of this.
Hey everyone,
Ever since I bought the TP2 I've had issues with every rom I tried. I started with a 6.1 build. not long after that several updates where released by HTC.. but I kept issues with crashing software, freezing etc. This both with a clean build and with some approperiate software installed. I did notice that when I used a backup program the system was more unstable than when it was a complete clean build.
After the 6.5 releases I was about to throw the phone out of my window. I tried a bunch of roms, from the simplest builds available to several others. But no matter what I try the phone keeps freezing, and crashing. I also have issues with the alarm not going off sometimes.
When I installed third party roms I used the recommended radio's. and I followed the instructions given, which includes whiping the system before I install a new radio and rom.
I've searched the web for this but I haven't found out what this could be, maybe any of you have a clue what the problem could be.
Thanks in advance!
Dion
Ownsta said:
Hey everyone,
Ever since I bought the TP2 I've had issues with every rom I tried. I started with a 6.1 build. not long after that several updates where released by HTC.. but I kept issues with crashing software, freezing etc. This both with a clean build and with some approperiate software installed. I did notice that when I used a backup program the system was more unstable than when it was a complete clean build.
After the 6.5 releases I was about to throw the phone out of my window. I tried a bunch of roms, from the simplest builds available to several others. But no matter what I try the phone keeps freezing, and crashing. I also have issues with the alarm not going off sometimes.
When I installed third party roms I used the recommended radio's. and I followed the instructions given, which includes whiping the system before I install a new radio and rom.
I've searched the web for this but I haven't found out what this could be, maybe any of you have a clue what the problem could be.
Thanks in advance!
Dion
Click to expand...
Click to collapse
What ROMs have you tried? When you say you wiped the phone, you mean you ran Task29? If not, I would highly recommend doing so before every ROM flash. Also after the phone boots up after the flash, hard reset to empty the storage memory, just to be safe. May or may not help, but can't hurt.
I run the ROM stated in my signature, and it very rarely freezes or crashes, and thats with the CPU overclocked to 729 MHz.
Most backup software is not meant to move from one ROM to another (and can cause a lot of problems is you do so), only for backing up and restoring within the same ROM. Try some research on the specific backup application you use, to see if this is the case.
I run the 21916 Energy ROM. I have tried several different ROMs and they all seem to pretty much work the same. The only ROM I have ever had crash or lock up on me is the factory TF3D based rom. I always use the task 29 and flash any rom I want to try.
Hope this helps.
First of all, thanks for the fast replies.
I've used task29 with every new flash. I might try it again without using a backup. And I will also try to overclock it a bit. I've done a dozen of hard resets allready, and I soft reset the device on a daily basis. Might this be a hardware issue if I keep getting the issues? If so could it be worth it contacting HTC ?
I think you misunderstand about the overclocking. Overclocking would INCREASE the chances of you having freezes and crashes.
Other than on SOD I got in the 1st week of owning my Tilt 2, all my crashes have been related to overclocking or something I was doing with the phone that I shouldn't have. Yes, I sometimes have to reboot the phone because TF3D has notorious memory leakage, but other than that my phone runs great. I read about a lot of people having random lockups when doing normal phone stuff (mostly TP2 owners) and I have to wonder if they just got defective phones. Other than that 1 unexplainable SOD, I know exactly why my phone doesn't behave as it should and it isn't that often. I've been overclocking it at 748 for a month without issue.
redpoint73 said:
I think you misunderstand about the overclocking. Overclocking would INCREASE the chances of you having freezes and crashes.
Click to expand...
Click to collapse
Well, in that case I will not overclock anything!
Which rom do you guys recommend as one of the lightest and most stable roms? if I got the same issue with a clean build I will put everything to stock and contact HTC about this.
The simplicity ROM that I show in my signature is very lightweight, smooth, and stable. Its the best I've used do far.
I will try that one without restoring a backup then. Many thanks guys !
Hello.
My Wildfire S has a vary nasty bug - screen is freezing after unlocking. Well, I can wait few seconds if i just want to start gmail app etc. But when the call is finished and i have to press the Red Button, screen is freezed and that's very annoying.
What should I do to get rid of that?
i have same problem some help?
Same problem here...need help<<<<<<
i some time press home button to make it work>>>>>
got a video
I got a video example for those who can potentially help but don't undertand me)
youtube. com /watch?v=IBOCQYZJK9k
And a question - does hard reset do the same as if I flash totally new official firmware? I meen, does HR leaves something after it or only flashing new firmaware can give my phone a totally clean (like just out-of-the-box) memory?
hm, when I did hard reset, no app left, but still seeing that bug...
I'm using it with official ROM too, but i want to know - does flashing new ROM means the same as hard resetting, or HR is a little bit "softer"?
If someone has experience in flashing phones and spotting this bug, can you try to re-flash?
I've got bad news. I flashed the phone by myself and that bug still is on. That means only one - we should go to the service centre and they'll have to deal with it
never experienced that bug. I have 1.35.707.3 CL48651 release keys.
Very strange, mine will hang for a second on the odd occasion but it's never that bad. Only bug I've noticed is sometimes when I power it off the 4 buttons at the very bottom stay lit, again that only happens every now and again.
Does that mean it's HTC sense's problem? Some people on 4pda(russian smartphone forum) say that their phones have been repaired in service centre by replacing touchscreen. I can't understand - is this hardware or software problem?
I have the same problem. Upon unlocking, right side of screen is not working for a couple of seconds.
Tried to hard reset, and it didn't help. Also tried diferent launcher, and problem remained.
Maybe bug in htc firmware. Has anyone tried flashing it with cyanogenmod of something like that?
dojik said:
hm, when I did hard reset, no app left, but still seeing that bug...
I'm using it with official ROM too, but i want to know - does flashing new ROM means the same as hard resetting, or HR is a little bit "softer"?
If someone has experience in flashing phones and spotting this bug, can you try to re-flash?
Click to expand...
Click to collapse
If you mean factory reset with hard reset, only /data and /cache are wiped.
Flashing a new ROM does wipe /system and replace the content with the new one, nothing happens with /data or /cache here, except within the ROM zip is a cleanup script.
Within /data is all userdata stored, settings, apps and so on (standart behavior, with links2sd its different), within cache is like the name says cached data of the system that shortens the system boot time and stuff like this. In most common you have to clear this before using a different ROM cause it could cause faults, but if the whole base of the rom is different you also have to wipe /data cause this can within this case also cause problems.
Sry, for the off-topic.
---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------
nestorkg said:
I have the same problem. Upon unlocking, right side of screen is not working for a couple of seconds.
Tried to hard reset, and it didn't help. Also tried diferent launcher, and problem remained.
Maybe bug in htc firmware. Has anyone tried flashing it with cyanogenmod of something like that?
Click to expand...
Click to collapse
Different launchers are only apps, they can't solve this problem when it's related to the lockscreen app, maybe switching to another lockscreen version can solve the problem.
same here, after unlocking left side of screen doesnt work until waiting a few seconds or touching other side
Diferent lock application didn't solve problem either. I tried that. I am using ripple lock now.
nestorkg said:
Diferent lock application didn't solve problem either. I tried that. I am using ripple lock now.
Click to expand...
Click to collapse
Could be that it's kernel related. Maybe it's just a big lag, because the CPU governor needs some time to switch the CPU speed after idle.
Swyped from my HTC Desire S
Tectas said:
Could be that it's kernel related. Maybe it's just a big lag, because the CPU governor needs some time to switch the CPU speed after idle.
Swyped from my HTC Desire S
Click to expand...
Click to collapse
It is weird that only right side of screen isn't working properly.
Hope it's not a hardware issue.
Cyanogenmod for wildfire s isn't out yet, so i can't try flashing.
Anyone with some definitive solution?
try without sd card. then reformat the card in a pc the again in phone. worked for me before i used the cm7 rom
greavey said:
try without sd card. then reformat the card in a pc the again in phone. worked for me before i used the cm7 rom
Click to expand...
Click to collapse
Tried this, used the CM7 rom, did what you said above, reverted to stock and im still in the same boat, this HAS to be software related, anyone got any idea's???
Ko_Ka said:
Tried this, used the CM7 rom, did what you said above, reverted to stock and im still in the same boat, this HAS to be software related, anyone got any idea's???
Click to expand...
Click to collapse
This is really doing my head in, its the only thing really ruining my enjoyment of the phone now that I have S-off!
I wiped cache, dalvik cache, sd card everything through clockwork before using the RUU flasher, it has to be software, is there a newer version of the RUU flasher since the 1.30.401.0?
Just a suggestion but temporary remove all your widgets to see if that is what might be causing it.
I found some widgets try to refresh once the phone is woke up even before the screen is unlocked. So I uninstalled any that I did not use.
Also you might try these setting in your build.prop file:
Code:
view.touch_slop = 12
view.minimum_fling_velocity = 30
gsm.proximity.enable=false
debug.sf.hw=1
windowsmgr.max_events_per_sec=80