Related
For about the last 2 weeks I keep getting a "Voice Command has quit due to low memory" with any ROM. Yes, I always do a hard reset after I flash the ROM. It shows up before I even try to install anything. I'm not using any auto install programs during this so they are just the plain ROMs. Free program memory is also at least 50 MB, depending on ROM with 30-35 MB in use. I've just been removing VC from the StartUp.
I went back and tried the April 1 Dutty ROM that I think ran fine when I first tried it but now gives me an error. I reflashed the stock AT&T ROM and everything was fine.
I'm also having issues with HTC Home Customizer v1 in that it runs fine for a while then stops and gives a string of directory errors. I've gotten this when installed on both SD and device memory. It happens after I install some additional software but doesn't seem to be related to anything specific and has occurred with 2 version of HTC Home.
Wondering if there is a diagnostic program to check for bad chips or anyone else has seen this. I've had the Tilt for a few months and it just started acting up.
Thanks
Cant think of anything but hardware issues that would cause that.....
If i were you, i would flash back to the stock rom and spl, and take it back to att for a new/refurb one
mwp_742 said:
For about the last 2 weeks I keep getting a "Voice Command has quit due to low memory" with any ROM. Yes, I always do a hard reset after I flash the ROM. It shows up before I even try to install anything. I'm not using any auto install programs during this so they are just the plain ROMs. Free program memory is also at least 50 MB, depending on ROM with 30-35 MB in use. I've just been removing VC from the StartUp.
I went back and tried the April 1 Dutty ROM that I think ran fine when I first tried it but now gives me an error. I reflashed the stock AT&T ROM and everything was fine.
I'm also having issues with HTC Home Customizer v1 in that it runs fine for a while then stops and gives a string of directory errors. I've gotten this when installed on both SD and device memory. It happens after I install some additional software but doesn't seem to be related to anything specific and has occurred with 2 version of HTC Home.
Wondering if there is a diagnostic program to check for bad chips or anyone else has seen this. I've had the Tilt for a few months and it just started acting up.
Thanks
Click to expand...
Click to collapse
Use KaiserTweak or Advanced Configuration to Disable the File System Cache, in most of the new ROM's they are enabled that is why it is using so much memory even on startup.
impalass said:
Cant think of anything but hardware issues that would cause that.....
If i were you, i would flash back to the stock rom and spl, and take it back to att for a new/refurb one
Click to expand...
Click to collapse
Yeah, that was kind of my feeling. Was hoping someone would say, "Oh, happens all the time, just hit CTRL three times, say the magic word and it will be fixed."
My USB connector is getting loose anyway. I got mine through work and we have a dedicated AT&T rep so hopefully it won't be a big deal. I just need to remember not to say the words Flash or ROM.
KDKobes said:
Use KaiserTweak or Advanced Configuration to Disable the File System Cache, in most of the new ROM's they are enabled that is why it is using so much memory even on startup.
Click to expand...
Click to collapse
I seems no one else has reported this problem (and you know the forum would be full of posts it was common) so that's why I'm leaning toward a hardware issue.
mwp_742 said:
I seems no one else has reported this problem (and you know the forum would be full of posts it was common) so that's why I'm leaning toward a hardware issue.
Click to expand...
Click to collapse
Have you tried what I had suggested? People do talk about it just in the ROM Development Forum where it should be. And just so you know the AT&T Tilt is an 8925 not an 8950.
mwp_742 said:
I seems no one else has reported this problem (and you know the forum would be full of posts it was common) so that's why I'm leaning toward a hardware issue.
Click to expand...
Click to collapse
Don't worry I have the problem too.. now I am searching for the tweak and will post result after I try it
maybe clear the temps files from pIE
I've seen this same problem three times since flashing dutty's April 1 rom about two weeks ago. Haven't spent any time to investigate it yet.
Sounds like a possible .net issue.
I know there were a few missing files from the Apr. 1 ROM.
First, try re-installing .net cf.
Then if you are using Opera delete the Cache files, Take a look for files in \Temp, \Application Data\Volatile, & the cache/history/temp files for PIE.
Thanks for all the input guys (and gals? - yeah right!)
Guess I won't send it in to the shop yet (especially if they replace with a refurb).
Hi all,
for some reason, when i mess around with my phone, and install stuff, the people tabs stops working, and its starting to really bug me.
It seems that when i install stuff it happens, like just now. I had some themes and a font installed, and the phone was running perfect, and now, i just installed something else, and the people tab has died!
Does anybody know of the reason for this? Do i have a faulty phone?
Shaady said:
Hi all,
for some reason, when i mess around with my phone, and install stuff, the people tabs stops working, and its starting to really bug me.
It seems that when i install stuff it happens, like just now. I had some themes and a font installed, and the phone was running perfect, and now, i just installed something else, and the people tab has died!
Does anybody know of the reason for this? Do i have a faulty phone?
Click to expand...
Click to collapse
I dont have any problems with this phone what so ever (using Duttys latest 2.5). To me it sounds like your installing faulty applications.
Its nothing that loads of people on here havent installed on their devices!
then you must be doing something wrong because this is the first i've heard of this problem
Actually I have the same problem. For some reason the entries of faforite people dissapear from the people tab. I run a stock Dutch ROM with nothing special...
Anybody know a solution?
Chris1974 said:
Actually I have the same problem. For some reason the entries of faforite people dissapear from the people tab. I run a stock Dutch ROM with nothing special...
Anybody know a solution?
Click to expand...
Click to collapse
Yup thats exactly what happens to me. Do you get an error report and then it goes back to the home screen and says launching touch flo 3d?
I run a stock ROM, and its really bugging me, because the good thing about win mo is that ability to install these kinds of apps, but im afraid to because the chances are it will bring back this errror.
I really don't understand why plp stay with crappy/buggy old roms... just because they are official... you should spend 10 minutes to cook one of the newest roms here around and you'll see how many steps they are forward to "official" ones
bye,
davide
suiller said:
I really don't understand why plp stay with crappy/buggy old roms... just because they are official... you should spend 10 minutes to cook one of the newest roms here around and you'll see how many steps they are forward to "official" ones
bye,
davide
Click to expand...
Click to collapse
Agreed....I hate to say this gents, but the original ROMs that HTC publish are not as good as you think they are
If I were you I would pick a resectable ROM that looks like what you require, set your PDA up and "flash" away all the quirks and bugs that HTC introduce to the device!
I know its not right, but thats life with HTC.......
Official ROMs are fine.... until you find this forum
then you start installing apps... tweaking... uninstalling... it all gets messy.
You baisically try and create what custom ROMs do on top of a 'Official' ROM. Best advice is to Flash a ROM, you can always put it back to 'out of the box condition' by flashing the SPL and Official ROM back (i've had to twice for repairs )
if you are talking about your favorites clearing, that happened to me when i moved the people tab. i bet your favorites are hard coded to that location so moving or altering it messes it up in some way.
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.
** 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)
Hi,
i'm new here, so i might seem a bit dumb and sorry for my bad english.
anyway, i tried using search, but i only found this SOD thing and that's not exactly what i have got. the thing is that my X1 freezes randomly. i.e. i put it charging for the night and when i wake up in the morning, my X1's screen is all lit up.
another example is when i just pull it out my pocket to check the time, it's either in SOD or same as the above: lit up and frozen.
when this occurs, the X1 is very warm and it doesn't respond to screen/button presses, the only thing that works is that small reset button in the back or pulling out the battery.
i don't really know, what is important and what's not, so if you ask, i can provide additional details. thanks for your help in advance.
it might help if you provide your current firmware (and version) and a list of apps you installed additionally and when it started (e.g. after installing xy|flashing rom xy|tweaking reg key xy|..., but as of now it just sounds weird
well, i'm currently on this Evilash Leo ROM and i haven't installed much programs, because i'm looking for a fast and stable ROM.
OS version: 5.2.21056 (21056.1.6.9)
Manila version: 2.5.20121412.2
ROM version: 1.05.911.15 WWE
ROM date: 09/10/09
Radio version: 1.14.25.55
Protocol version 52.65.25.34U
currently i have only installed Opera Mobile browser, version 10.00
the problem started when i started flashing my phone. my first ROM was from Valkyrie, but it had some issues with displaying stuff on screen (phone lock icon, scroll bars etc.).
then i switched to Energy ROM and on that ROM this problem occurred for the first time.
at first i thought that it was because i used XperiaTweak and Advanced Config, but when i reset all values to their defaults and even tried reflashing, the problem persisted.
i have never touched the registry.
my usual set of programs includes (newest versions available):
Opera Mobile browser
Skyfire browser
Resco Radio
OpnMarket
Microsoft Marketplace
Julien Manici WiFi Remote Access
my first suspicion would be it could be rom specific, but as it started with NRGZ's and I'm a regular visitor there I can't remember hearing of similar occurrences
what you might try is flash back to latest stock rom, then reflash the custom rom of your choice and see if that helps
I hear that helps for some specific problems after flashing custom roms, I can't guarantee it will help you, but it might be worth a try
apart from that I can't come up with something more intelligent, maybe I get another idea
cheers
can i flash to any stock ROM, or it needs to be the same language as it was on this phone initially? and how do i exactly flash to a stock ROM? just change the name to KOVSIMG and the extension to .nrg (currently it's .image) and do as with any custom ROM?
i also wanted to ask whether i need to do something specific before/after flashing a custom ROM that i might have forgotten or use some programs/format my memory card etc.?
drizzy said:
can i flash to any stock ROM, or it needs to be the same language as it was on this phone initially? and how do i exactly flash to a stock ROM? just change the name to KOVSIMG and the extension to .nrg (currently it's .image) and do as with any custom ROM?
i also wanted to ask whether i need to do something specific before/after flashing a custom ROM that i might have forgotten or use some programs/format my memory card etc.?
Click to expand...
Click to collapse
I would try the generic one for your country, if there is one
rename it to KOVSIMG.nbh only if you flash sd method
backup your personal data
you might consider task29 from agent, but read the des and last pages of the thread carefully before you decide
well, i did as you suggested. didn't quite understand how to backup stuff with UC and Sashimi, but i found this app called SKTools, which got the job done.
after that, i have once encountered this strange thing, which is hard to describe. something like all my screen colors became different shades of white or something. i could still use the phone though, so i just did a soft reset.
the freezing problem occurred a couple times too, but i think that this time it was the ROM (correct me if i'm wrong). currently i'm using the Evilash Leo ROM and when i scrolled to the Twitter page, pressed the "All Tweets" button and scrolled to either my mentions, direct messages or favorites it showed nothing and a couple secons later it froze the way i mentioned in the first post of the topic.
other than that, no random freezing yet (i flashed this ROM at about 2 PM, and right now it's 11 PM here). Thanks for the help!
drizzy said:
well, i did as you suggested. didn't quite understand how to backup stuff with UC and Sashimi, but i found this app called SKTools, which got the job done.
after that, i have once encountered this strange thing, which is hard to describe. something like all my screen colors became different shades of white or something. i could still use the phone though, so i just did a soft reset.
the freezing problem occurred a couple times too, but i think that this time it was the ROM (correct me if i'm wrong). currently i'm using the Evilash Leo ROM and when i scrolled to the Twitter page, pressed the "All Tweets" button and scrolled to either my mentions, direct messages or favorites it showed nothing and a couple secons later it froze the way i mentioned in the first post of the topic.
other than that, no random freezing yet (i flashed this ROM at about 2 PM, and right now it's 11 PM here). Thanks for the help!
Click to expand...
Click to collapse
you are welcome, though nothing much done on my part
you think the rom might cause probs so I can only advice on checking the respective rom thread for similar reports, if you find them it might confirm your suspicion and even lead to a solution, if you find nothing post your experience there and check for feedback, maybe it got encountered but not reported yet and if it turns out that you are the only one using that rom suffering this problems it probably isn't rom related and you are still looking for a conclusion, but at least you can discard one possibility
gl anyway and have fun
cheers