Related
Last night I got a popup saying that my storage memory was low. it was at .05mb. I thought this was a bit low, but I went and deleted some stuff and got it up to 5.5mb. I then actually watched the memory count down to .01. I dont know if this is a virus or what. I tried to use sprite but it didnt work, also there is an icon was added to my HTC launch page, looks like a piece of paper witha windows symbol.
i have HTC Home, touch cube, kaiser tweak, voice command, garmin xt, just the basics. Please help
try clearing the browser's cache. the same thing happened on my old ppc even though I know I didn't have much installed, but clearing the cache fixed it.
I dont think it was the cache that was the problem but i could be wrong, i kept deleting stuff and nothingi did worked. Also when i hooked it up to sync it just kept cycling through the sync.
Needless to say i just did the hard/doft reset back the the beginining. Now I have to decide whether or not to reinstall all the programs or flash the rom
Are you using a cooked or stock ROM? A lot of cooked ROMs will contain fixed-size page pools, and while they are great for performance, they tend to have memory leaks.
i am using a the stock rom
None of the programs you listed are known for causing memory leaks, so I would reload all of them as usual, and see if the problem returns.
It may have just been some registry corruption causing it.
Well Windows is know to cause Memory issues.
Best thing I can recommend is a Hard Reset and Restore all your programs.
thelaserman said:
Last night I got a popup saying that my storage memory was low. it was at .05mb. I thought this was a bit low, but I went and deleted some stuff and got it up to 5.5mb. I then actually watched the memory count down to .01. I dont know if this is a virus or what. I tried to use sprite but it didnt work, also there is an icon was added to my HTC launch page, looks like a piece of paper witha windows symbol.
i have HTC Home, touch cube, kaiser tweak, voice command, garmin xt, just the basics. Please help
Click to expand...
Click to collapse
I see you're using Garmin XT, now i don't use that program, but does it download maps? I know that most mapping programs can chew through memory like you wouldn't believe. I use all the other programs and have never run out of memory before...of course truth be told, i've never left a rom on for very long either...
I must have flashed and reflashed my device about 20 or 50 times trying this and that; even started a few threads concerning the kaiser dying at startup because of a bull**** low battery message and had to get to bootloader. Just finished a triple reflash reinstalling cabs A to Z just fine, and as soon as I installed batti 2.0, 2.4, etc; in all three cases I got the dead battery tone of death. This is certainly not the first sec or third time it's happened, as it was my first virgen exp. with kaiser; or am I just retarted?
So let me attempt to distill what you just said.
You've tried many ROMs. The problem does not present itself until after installing Batti. Or has it been a problem ever since you first installed it?
I've never tried it, I use BatteryStatus.
It's a problem that many have experienced with the kaiser "tilt" within these forums, and to most of the people I personally know that own the device; Getting the low battery tone of death. Talking to to a few of my chip processor engineer buds; it looks like it's a combination of an overheating issue, combined with a batti app that tells the device to shut down. Installing cabs is taxing, especially when you have a few short of a hundred. Installed in increments and everything is gravy so far...
Ummmmmmmm... Okay. I think I'll have to re-read that later when I've woken up more.
i've flashed many roms, and i always install batti.. i don't have trouble with it..
Hi guys, I have had my Xperia a few days now, it's a Vodafone that I hae flashed the Generic UK software to (without HardSPL) it seems to work ok but I am having a few problems. First of all, whether or not the phone will boot is hit and miss, it will get to the today screen and lock up as soon as the clock on the today screen loads. Hitting the reset switch under the cover will reboot it and it will generally boot fine, usually on every second boot.
Another problem I have is that Shell32.exe crashes a lot as does explorer.exe Shell32.exe seems to crash when installing and uninstalling applications, it does not always happen but it's happened a few times so far and is becoming irritating.
I am going to reinstall the firmware image and leave it a day or two without installing any apps to see if the problem is resolved. If anyone has any posible ideas I would appreciate it. Thanks.
Edit: I have renamed thread to remove the reference to boot problem with memory card inserted because after having removed the memory card the problem still persists so I gues it's unrelated.
Shell32.exe error
I also am having issue with shell32.exe crashing, the problem is repeatable everytime I go into the today screen options, as soon as I exit, regardles of which panel I went in from, shell32,exe crashes and I have to reboot the phone. Sometimes the only way to do so is to remove the battery. Any changes that I have made in the today screen do show up after the reboot. This is really annoying me now as shell32.exe is an important system process. Any thoughts, or shall I just hard reset.
R2AA
I'd make sure you're updated to the GENERIC UK R2AA ROM, if you're already on it, get a new copy of it from here, reformat your mem card and flash the phone again.
I seem to be OK now and not getting the shell32.exe crash anymore. Still having various other problems with it stopping responding (barely anything installed, and nothing really running) but not much more I can do, just learning to deal with it because i can't do with the stress of worrying about it. It's Windows, so expect it to suck.
i was on my R1A, had this problem, Hard reset it and the problem still exist...
Upgraded to the official R2AA10 and guess what? the problem is still there....
What is it that actually causing this problem? im planning on selling my X1 because this problem is so irritating....
Strange
mr_sheen said:
i was on my R1A, had this problem, Hard reset it and the problem still exist...
Upgraded to the official R2AA10 and guess what? the problem is still there....
What is it that actually causing this problem? im planning on selling my X1 because this problem is so irritating....
Click to expand...
Click to collapse
Strangely, I stoppped having this problem a long time ago. I ran on R2A and R3A for a long time without any trouble now, I think it was due to a common program we were having installed because I use different programs than I used to and I havn't seen it happen since I last posted about having the problem.
Stick with a fresh install and see how it goes, install your apps slowly until it doesn't happen anymore.
I can't remember the exact programs I used to use but I have a feeling it was related to homescreen plugins or some such.
Let me know what programs you use maybe we can find a common denominator.
alias_neo said:
Strangely, I stoppped having this problem a long time ago. I ran on R2A and R3A for a long time without any trouble now, I think it was due to a common program we were having installed because I use different programs than I used to and I havn't seen it happen since I last posted about having the problem.
Stick with a fresh install and see how it goes, install your apps slowly until it doesn't happen anymore.
I can't remember the exact programs I used to use but I have a feeling it was related to homescreen plugins or some such.
Let me know what programs you use maybe we can find a common denominator.
Click to expand...
Click to collapse
Okay, so after hard reset, i always install my program again one by one...
Strangely, the error always happen the FIRST time i install any program that uses today plugin...at first i thought it was SPB Wireless, then after another hard reset i installed Beejive, and the same error occurs...
Now mine is a little bit stable, mainly because i dont touch the today setting anymore....i (forcefully, despite the error ) installed Pocket digital clock, SPB Pocket Plus, and SPB wireless....
Its been fine for the last 2 days...without touching any of the today settings...
What is it that actually causing the problem? so strange....
mr_sheen said:
Okay, so after hard reset, i always install my program again one by one...
Strangely, the error always happen the FIRST time i install any program that uses today plugin...at first i thought it was SPB Wireless, then after another hard reset i installed Beejive, and the same error occurs...
Now mine is a little bit stable, mainly because i dont touch the today setting anymore....i (forcefully, despite the error ) installed Pocket digital clock, SPB Pocket Plus, and SPB wireless....
Its been fine for the last 2 days...without touching any of the today settings...
What is it that actually causing the problem? so strange....
Click to expand...
Click to collapse
Well, I never used SPB wireless when i had that problem, but i did use Beejive, Vito Sound Explorer (has a today plugin) HomeScreen++ and Wisbar Advance Desktop (saw a few crashes with this). Saw the problems a lot back then.
When I only ran Homescreen++ I never saw the problem.
I am running 6.5 now so i can't test it for you I'm afraid to find the exact problem, but I'd certainly keep hold of your Xperia because it's definately just caused by a 3rd party app/plugin.
alias_neo said:
Well, I never used SPB wireless when i had that problem, but i did use Beejive, Vito Sound Explorer (has a today plugin) HomeScreen++ and Wisbar Advance Desktop (saw a few crashes with this). Saw the problems a lot back then.
When I only ran Homescreen++ I never saw the problem.
I am running 6.5 now so i can't test it for you I'm afraid to find the exact problem, but I'd certainly keep hold of your Xperia because it's definately just caused by a 3rd party app/plugin.
Click to expand...
Click to collapse
the weird thing is, i ran all my program above for about 4 months on my R1A and no problem occurred....everything was good.
Then i tried to install SPB phone suite, but the installation stopped at 3/4 because the software wasnt signed or something like that (strange, i got it from SPB site), and it just left me some today plugin but withoun any name...it was blank....my today plugin order was in a mess too...i soft reset, it was okay....but i soft reset it again later that day and thats when the problem happened...
I found it strange that it still happens after hard reset and even after Rom change...especially to ANY program that uses today plugin....weird...
Try using R2A_10 or later, I never had any problems from then on, I'm running gtrabs R3A/6.5 atm, although it hasa bunch oof problemsof its own.
alias_neo said:
Try using R2A_10 or later, I never had any problems from then on, I'm running gtrabs R3A/6.5 atm, although it hasa bunch oof problemsof its own.
Click to expand...
Click to collapse
im using the official R2A10 at the moment....the problem still exist the first time i put all my software back....
But it seems stable now for the last 2 days...if the problem occurs again, i'll post it up here,,,
Re: PARANOIDANDROID 3.00 | Only Rom on Android capable of Hybrid mode 02/11
Edit: XDA freak out
decalex said:
ya, that's not gonna happen, BUT, xposed framework mod works on TW based ROMs, and u could always go that route if u want per app DPI. I'm a big fan of PA's implementation though. Xposed works great but a little more tedious.
Click to expand...
Click to collapse
How did this got here?
Lmao, I have noo idea.
Hi! For a while I've been searching for a reason why my phone seems to freeze almost daily while charging or before / after I snooze a morning alarm. And sometimes during the night, maybe it's random. By freeze I mean the phone is sleeping and when I push the power button nothing happens. The only way to restart it is to take off the cover and either remove the battery or press the little reset button.
I use itje's ROM with standard WM6.5 and Manila 2.1. I tried diferent builds and newer Leo ROMs, but I always get the same problem. It didn't happen some time ago when I was using WM6.1 + Manila 2.0.
While searching in the forums for solutions, I noticed there are some users with the same random freezes using various ROMs from different chefs. But most of the users don't seem to have this problem, which is weird. I guess the hardware should be the same, so does anyone have any idea why this freezing happens only to some of us?
I tried different methods and ROMs, countless hard resets and re-flashes, even additonal Stock-SPL and Hard-SPL, but nothing seems to work. It even happens if I install no other programs and don't have the SD inserted into the phone, only my SIM card. So it's not from external programs (like G-Alarm) either.
Well, any helpful information or advice? Thanks!
I am experiencing the same problem. If anyone got a solution for this, please share.
Regards, Eduardo.
i have the same problem to but only with the cooked wm 6.5 roms and higher not with the rom that came with my x1
i get the same problem. i'm using itje's Touch I-T Xperience 15 6.5
Now I flashed a WM6.1 ROM with Manila 2.1 to see if I still get the problem. Do you think our phones have a problem with the Windows 6.5 builds or maybe the problem is with Manila?
Did anyone try to live with one of these ROMS for a few days with Manila disabled to see if you still get the freeze? Maybe I'll try this also after I finish my 6.1 test. It's very annoying that we don't even know the cause for this freeze yet...
have the same problem when using 6.5 but when on 6.1 nothing of the kind...
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Well, I can confirm that on various itje 6.5 ROMs I get the standby of death without installing any alarm program. I didn't install ANY programs, for what it's worth. And others can use G-Alarm 2.3 and don't get this freeze.
Didn't use Valkyrie ROMs yet. I'm testing now Touch X 10.8.2 and I have G-Alarm 2.3 installed. Let's see if it dies in the next 48 hours while on a 6.1 build...
Here is my experience...
I never got standby freeze issue(never used G-alarm/Klaxon), but i do get black screen or garbled screen issue randomly while receiving call irrespective of the ROMS(wm 6.5/6.5.1).
Only one time almost a week i didnt face this issue, then later problem repeated. So i realized that week i've used COM4 build. So for testing it i tried again same one for a week and problem didnt exists. Since the ROM which i used has default X1 dialer which i didnt like at all.. so got updated to other ROM and started face the same issue
Maybe some of us have a slightly different harware in our X1 that triggers this freeze, but only in WM 6.5?
So far the WM6.1 + Manila 2.1 is working fine, lots of customizations made by me after flashing too. G-Alarm managed to wake me up OK.
Darkchaser said:
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Click to expand...
Click to collapse
Well you can count Valkyrie 4.5.502 out because i installed it yesterday and this morning after my alarm went off about 20mins later the phone frooze. I have been experiencing this for the past months and i REALLY hate this phone now. I have tried all sorts of tricks from reseting the phone around 9pm to just not running ANY program and it still freezes. I have tried all sorts of roms with the exception of Touch X 10.8.2. I guess i might as well give that one a try. I will keep an eye on this thread for a solution.
On an older Valkyrie TR build I was getting the problem and I fixed it by doing a soft reset with the SD card out, waiting for everything to load up and run nicely, then inserting the card again. Went to the music tab and waited for it to load all my tunes and the same with photos. Didn't have the problem after that, but I was only on that ROM for about a week.
I thought it may be related to usb port driver issues in WM6.5, but it could also be the audiomanager in manila or some conflict between a WM6.5 process and a manila process.
Anyway, will be trying 4.4.81TR Valkyrie and see...
But the biggest question is why some (most) people never have this problem...
Never seen this problem on WCX 22001 Pure wm6.5 rom and I'm using it for about one month. I've installed many apps and my X1 works great with battery about 2-3 days using WIFI, BT, and all other stuff. No Manila - no problem in this case. It's an older build of WM6.5 but with newer builds WCX Rom users didn't complain about freezing problem or alarm issues.
So maybe it's Manila?
Today I wanted to flash Itjes newest ROM but I'll wait for solution couse my phone should wake me up today
Can program your phone Lockscreen has frozen the rechargeable device. Best before charging you restart your phone and not run any programs.
yes i get this problem too.. every morning my phone is off.... so it really needs to be looked into.. it seems to occur from more recent builds of 6.5..
i was previously using a wild child pure rom from about 3-4 months ago (6.5 early build)... this issue never happened...
then recently i upgraded to the V11 Unoff series and now it occurs.. and is obviously occuring for a lot of people with other recent builds of 6.5...
if the solution is ever found please let us know....
I might be completely off here... but I used to have this problem often, in addition to having slide to unlock malfunction on me, even with the newer rom builds.
When I unchecked the boxes that said display owner information/notes when device is turned on, both problems were gone - it might just be a coincidence though and I've only been testing it for 2 days.
Hey guys,
I've been having the same problem, only that this are the situations in which I faced the issue with my X1i (and managed to replicate the freeze):
-Receiving SMS while charging (no pc conection)
-Charging while alarm goes off (again no pc)
-When task or appointment announcement sets itself to sleep (i.e: you ignore it) while charging. (go figure, no PC)
-When after ignoring (not hitting dismissed button) task or appointment screen shuts off (Running on battery)
I've also gotten the problem in other situations, but i couldn't replicate them. The only Thing I did notice was that there is a growth in the rate this happens over a span of 3 days after flashing/hard reseting. In my case, it was one increment per day (ie: 1st day, happened once; 2nd day, twice; 3times the 3rd day.. then, i reseted or replicated, so my statistics went down the pipe )
Other thoughs: what radio are you guys using? maybe we can narrow it down to a radio as well. Thus far I've seen it narrowed it down to Manila 2.5, but then others do not have this (and then there me, with Manila 2.1, that has it ). I changed my radio y-day and hasn't happened yet (xing fingers though...) wil try to replicate tomorrow after my alarm wakes me up
My info:
X1i Black (came with R3 generic UK ROM, Radio. 1.14...)
Issues happened with: Radio 1.10.25.18 (Installed with NRG's ROM vOCT 28)
ROM info: (see signature..)
Manila: v2.1.191...
Current radio: 1.14...
Carrier: AT&T US
I tried to contribute as much info I could get about this issue... hope we can get it solved.
I'll try to flash again a WM6.5 version to see what radio will be installed. This week I needed my phone WORKING , so I used a 6.1 ROM.
I didn't find a pattern for my freezes, but I think it mostly happened while charging from the outlet, or in the morning before the alarm went off (very bad thing to happen), or after I snoozed the alarm (again, very bad).
I read somewhere that it's useful to format your SD card before flashing. I don't see how this could help, but I'll try to flash via USB or from another newly-formated SD card. I always flashed with kovsimg.nbh on the SD root and I only formatted it when I got the phone, 9 months ago...
Also, some say it's good to flash first an original ROM, hard reset, then install the custom ROM again. I tried that, even stock-SPL and hard-SPL again, but didn't seem to work. Maybe I had 48 hours without freeze, but then it started again.
@8SE8 - I never had those options checked, so we can rule that out I guess.
I have been reading about this issue here and in another forum - mainly
because I had seen it only one single time. It actually occured when I was
loading the device during the night. I do not remember which ROM it was
exactly, except that it was an itje ROM with Manila 2.5.
Then, I went back to Manila 2.1 and WinMo 6.1, Touch_X 10.X.X. Must say,
that is still my fallback ROM, it feels extremely fast, it is stable, memory
usage is low - what else to wish?
Next, I went to the multilanguage Rhodium based Manila 2.1 and WinMo 6.5
from itje in my own language. After installing FM Tuner, a correct dialer and
some tweaks, it is also very fast and stable, memory usage at 50%. No more
soft resets since almost a week now, no "stand-by of death".
The difference to others is maybe: I do not flash using the SD card, always
with the USB connection. Is this provoking the difference? I cannot imagine,
but this is what I can contribute here.
** Please check post #2 first. It looks like we have found a solution. **
We don't reprimand anyone for asking questions, so feel free to ask (preferably after reading or searching the thread) if you have doubts.
I'm starting this thread in the hope that we can determine and find a cure for the lockup issue some of us have been dealing with in the later Manila 2.5 version ROMs.
This is something I've been trying to deal with for some time now and it seems more widespread than people realize from the number of posts by users who have had this issue.
Let me explain my definition of "lockup":
1- It always happens when the device is in sleep mode, never while it's used.
2- Never happens with stock ROM or Manila 2.1, only on Manila 2.5.
3- It's random, could happen any time of the day, in any frequency.
4- It's more likely to happen with some ROMs than others, leading me to believe it is related to the ingredients used in the kitchen (that is: operating system/software ) The "lockups" will start within the first 24 hours and possibly become more frequent over time.
5- It's highly unlikely that any sw installation is responsible for this (NeoS2007_Driverpack_3 excluded, I haven't done sufficient testing with it)
6- When the "lockup" occurs, the screen lights up (you can see it does in the dark) but the device is unresponsive. If you wait for a while, the home screen appears but the device is unresponsive. The only way out is taking the battery out or doing a soft reset.
7- Using MTTY or flashing a stock ROM may help fix other problems but does not help for this specific case, the "lockup" will still occur.
8- It's entirely possible (but hard to determine) that hardware may be an issue here. The fact that some people always have this problem and others don't, may be due to different hardware revisions, if there are any.
9- This problem is very specific and never leads to a hard reset.
10- When the lockup has occurred, people calling may hear the phone ringing but the HD remains unresponsive and there is no call logged, so at least the radio section is working.
Please post you experience with this issue, including the ROM involved, and any action you have taken that leads to a solution.
Please also mention whether you flash using SD card or from the PC. Since none of my SD cards work, I always have to flash using my PC, so that is something I need more info on.
Please read this post to be uptodate on the latest situation with this issue
Quite a number of new sys versions seem to be causing lockups on most HDs. This is a sys problem and is not related to the lockup with the video drivers but is related to the OS version. If you are using a ROM with a new sys version and are having lockups, just switch to another ROM with a different sys version.
As the number of pages in the thread started to increase, I want to post a summary of our findings here.
As stated numerous times, not everyone suffers from this problem but the number of people who do suffer seems to be much more than I originally thought.
Please remember that we are talking about a very specific kind of lockup here as explained in post #1.
So far, our findings indicate that it is a combination of conditions that cause this issue. If Manila 2.5 and the Neo's Driver pack are used together, this lockup will occur on those HDs that are prone to this issue.
mnet has prepared a cab that effectively deletes the driver pack and restores stock drivers. If you are having this problem on a Manila 2.5 ROM, you should try this. Needless to say, before trying this, you should have already tried the recommended cures, like flashing a stock ROM or using MTTY.
You can't actually delete the files cooked in the ROM, only replace them...Some dlls from Neos drivers remain in the windows folder, however they are no longer used due to registry modifications.
Several users who have been suffering from this lockup have confirmed that after applying mnet's cab to uninstall the Neo's Driver Pack, the lockups have stopped. So, it's a definite cure.
Cab to remove Neo's Driver Pack.
Also, please check this post. It may be worth giving it a try if you have unexplained lockups.
The Topaz D3DM drivers also seem to be causing lockups, confirmed by other users.
Mikenificent BlackStone TestDrivers seem to be safe. I tested for a few days and no lockups occurred.
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?
Fallen Spartan said:
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.
I only had this with Dutty and Miri's 21xxx series with Manila 2.5.
Once I went to 28xxx series, from PDAViet, Energy etc, this hasn't happend again.
So I'm guessing its WM6.5 21xxx and 23xxx related rather then manila.
Also, it happens far less when you use a lightweight (short and low bitrate) sound for notification.
It seemed to happen for me whenever the "new mail" or "new sms" notification was supposed to sound.
When putting a very short sound, it stopped freezing. When putting back a long sound, it would freeze up more often.
bobsbbq said:
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.
Click to expand...
Click to collapse
A number of people have stated that they get issues with cooked roms (while others don't) if they are constant flashers, and the common solution would be to flash a shipped rom and then back to cooked. As I stated above I've been fortunate enough not to experience this so haven't had the need to flash a shipped rom. But from reading users issues this isn't a clear cut problem as it doesn't affect everyone
homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
I've ruled that out. I always install the same set of applications, same email etc.
Never have this issue on stock ROM or Manila 2.1 ROM, only on later M2.5 ROMs, so it has to be related to M2.5 somehow.
Xannytech has been very helpful, comparing ROMs where I had this issue with a few ROMs where I don't have it, it seems that the problematic ROMs are larger in size. So perhaps there is a problem with the NAND memory and the bigger size ROMs use it whereas the smaller size ROMs do not use it. This is the reason why I mentioned hw revision as a possible cause.
Fallen Spartan said:
Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
It does happen on a bare ROM, no data sync, no SD card, no applications installed. Just flash a new ROM and wait, it will happen.
I guess it would be OK to mention here that currently the only ROMs where I don't have this issue is with Miri's ROMs (which are smaller in size than others).
wow.. luckily i came through this topic before i sent my HD for repairs.. and i thought it was the touch screen that has malfunctioned..
u are right, it only happens when the device wakes up from sleep.. if ur lucky, u could press half the screen and re-calibrate the screen.. if ur not, then hard reset is the only way for u to re-calibrate ur screen..
currently using;
GridLeo 1.7 (1.2.5.30),
OS (5.2.21869)
Manila 2.5.19201130.0,
Radio (1.14.25.24)
termignoni said:
wow.. luckily i came through this topic before i sent my HD for repairs.. and i thought it was the touch screen that has malfunctioned..
u are right, it only happens when the device wakes up from sleep.. if ur lucky, u could press half the screen and re-calibrate the screen.. if ur not, then hard reset is the only way for u to re-calibrate ur screen..
Click to expand...
Click to collapse
This doesn't appear to be the same issue. If you take the battery out and restart your HD, things should get back to normal - for a while. This never leads to a hard reset.
For your case, I suggest you flash a stock ROM and test with it for a while.
makbil said:
This doesn't appear to be the same issue. If you take the battery out and restart your HD, things should get back to normal - for a while. This never leads to a hard reset.
For your case, I suggest you flash a stock ROM and test with it for a while.
Click to expand...
Click to collapse
As you say, removing the battery or soft reset resolves the issue, but not for long before it happens again (unresponsive screen after sleep, but backlight lights up when i tap the screen)..
this is what is going on with my HD.. until one day, even after soft reset, i could not enter my pin or even access the calibration screen as i could only "tap" the top half of the screen..
after many soft resets, i could only "tap" the top half.. hard reset resolved my problem until a couple of days back, where the problem seems to start again.. this has been going on since last month, and out of the blue..
termignoni said:
As you say, removing the battery or soft reset resolves the issue, but not for long before it happens again (unresponsive screen after sleep, but backlight lights up when i tap the screen)..
Click to expand...
Click to collapse
I never got as far as having to do a hard reset but I guess it is possible after extended use.
I recommend you flash a stock ROM, use it for a while. When you are sure you don't get the lockups any more, flash your favorite custom ROM again. This should prove that the culprit is ROM related and not a hw problem with your HD.
makbil said:
I never got as far as having to do a hard reset but I guess it is possible after extended use.
I recommend you flash a stock ROM, use it for a while. When you are sure you don't get the lockups any more, flash your favorite custom ROM again. This should prove that the culprit is ROM related and not a hw problem with your HD.
Click to expand...
Click to collapse
i suspect it's a ROM issue as well, as i never had this issue with any other ROMs with the old Manila.. i'm gonna flash to the stock ROM tonite and see how things go.. but even so, i might take more than a week before it's showing signs of mis-calibration..
termignoni said:
i'm gonna flash to the stock ROM tonite and see how things go.. but even so, i might take more than a week before it's showing signs of mis-calibration..
Click to expand...
Click to collapse
If you do have this problem on a stock ROM, then definitely it's a different problem. Just remember to flash the stock ROM by running the executable and not through running the BlackstoneRUUWrapper + nbh file manually.
I've had this problem for the past couple of months whatever Rom i use and whatever software i install.However, I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
http://forum.xda-developers.com/showthread.php?t=540290
bodgeman said:
I've had this problem for the past couple of months whatever Rom i use and whatever software i install.However, I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
Click to expand...
Click to collapse
any reference to this "MTTY thing" u did? i might give a try 1st..
bodgeman said:
I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
Click to expand...
Click to collapse
I also did the MTTY thing but had the lockup within 24 hours on Xanny's Evo 1.6. Keep a close eye on this, if you don't have it within a few days your problem may have been cured
Didi you flash from SD card or from the PC?
termignoni said:
any reference to this "MTTY thing" u did? i might give a try 1st..
Click to expand...
Click to collapse
Here . My results are on page 50.
makbil said:
Here . My results are on page 50.
Click to expand...
Click to collapse
thank you..
btw, this time i flashed using PC instead of the SD card..
one more thing to add, the first time i did my hard reset, i restored my device using PIMBackup (restored everything).. within 24hrs, it happened again..
the 2nd hard reset, i restored only my Contacts and till now (after 3weeks), only it's starting to happen again..
i don't know bout u, but this is how it's happening to me..
- at first, u'll notice a slight mis-calibration while typing an sms or selecting something (after screen calibration, everything went fine)
- then, after a few days, same thing happens (can't tap the bottom part, soft reset and screen calibration solved this)
- and today, after my device woke up on sms, i could not unlock (using the default WM6.5 lock screen - had to soft reset twice, then calibrate screen)