I seem to be having some biig issues with my tilt and was hoping for someone to shed some light on the situation for me, I have a tilt, now running on hyperdragon IIIr , hard spl 3.56 and a emonster radio, ever seince I've unlocked it and flashed the a rom I've ran into oone of two issues 1. rom works fine with exception to heavyish lag on typing that forces me to type slow (E.G. duttys 19716 hybrid) and I do a lot of typin so the lags is a big issue 2. running currrrently beforemention hyperdragon IIIr and emonster radio, (although I've had the issue on other radios) and it runs fine at first, I tap the power button don't use it for 20 mins or so then when it turns back on it either steps in from dark to bright and will be VERY unnresponsive like having to tap the windows button 20x times before I get one tap I've been flashing like a madman tyig tofind a rom that generaly works... PLEASE HELP
Learn to use search. I, as well as many other people, have the lag issue. It's been mentioned before.
The other issue could be either your device, ROM, or radio. Change to an official radio. If you still have the same problem, try going back to the stock ROM. If the problem continues to exist, it could be your device.
If it turns out to be the radio, simply change radios.
If it's the ROM, address it in the ROM's thread, not in a new one in a different forum.
If it's your device, you had better learn how to get it back to it's OEM state, provided you have a warranty.
Also, spacing, punctuation, and spelling tend to be helpful when seeking help. I'm not saying it has to be perfect, but it's nice for it to be understandable without having to analyze it twice.
Now, run along and play.
mr4r4n said:
I seem to be having some biig issues with my tilt and was hoping for someone to shed some light on the situation for me, I have a tilt, now running on hyperdragon IIIr , hard spl 3.56 and a emonster radio, ever seince I've unlocked it and flashed the a rom I've ran into oone of two issues 1. rom works fine with exception to heavyish lag on typing that forces me to type slow (E.G. duttys 19716 hybrid) and I do a lot of typin so the lags is a big issue 2. running currrrently beforemention hyperdragon IIIr and emonster radio, (although I've had the issue on other radios) and it runs fine at first, I tap the power button don't use it for 20 mins or so then when it turns back on it either steps in from dark to bright and will be VERY unnresponsive like having to tap the windows button 20x times before I get one tap I've been flashing like a madman tyig tofind a rom that generaly works... PLEASE HELP
Click to expand...
Click to collapse
It almost sounds like you installed an application that is causing your device to freeze up. Also, remember to hard reset after flashing. If you can please list the applications and sips you have installed and maybe someone can point out the culprit.
trust me spelling is never normally an issue but im typng from the device, unfortunatly I don't have a home computer at the moment. I've used search, I just haven't come across anything that matched my situation, the best working rom so far was duttys apr 29 hybrid. I've done some different radios and if anyone would be able to id love to read whatever setups you guys have on your devices thatwork and whatever issues you guys may be having btw my hard spl is 3.56 as well. I mean alll I wanted was 6.1 style messaging a good strong antenna (emonster is working well) if the roms fome with extras cool, if not its all good, I just need the device to work, thanks for all you help people
and btw the issue with the major slowdown is after flash (and hard reset) when I first tap the power button to put it on my belt for later no apps installed
This will be tedious, but try going back to AT&T Stock and see if you're still having an issue with the slowdown. Also, you might want to try looking for the Tilt Keyboard fix and trying that first. I still have lag with it, but it's worth a shot before you go back to stock.
If you still have issues with the stock ROM (try the stock SPL too if you can, there's instructions for going back to OEM you can click here to see those)
If you have the issue with everything set to stock, it's your device itself. If the problem goes away after reverting to stock, then try re-doing the whole SPL and flashing process for the ROM of your choice. At that point, you may wish to consider addressing your issue in that ROM's thread.
you are a genius, i ran it from the beginning and started it from scratch, i started with a light rom the new Hyperdraggon IIIr emonster rom and then hard spl'd at 3.29 (after i did the whole re stock and unlock process) im guessing i might not have done it right from the start and or the 3.56 spl might have been the problem also but its acting sufficiently well now i will keep you guys posted thanks for the support
I have 3.56 and have no problems. I almost always use a light rom and throw EVERYTHING onto my storage card. You also might trying running Pocket Mechanic
Related
Been following this site for weeks and it is getting more popular eacha nd every time someone buys a Diamond phone, so keep up the good work.
I have finally decided to see what I can do with mine by upgrading the ROM and I would appriciate any advice you guys can give me as i am a totally newbie.
Here are the details:
It is on T-Mobile (UK)
Version -
1.37.110.3 WWE
06/20/08
1.00.25.03
Thanks
Hello there!
Not sure what you mean by upgrading the rom? Guess you mean applying a cooked rom?
A cooked rom is one thats been customised and is flashed over the top of your current rom, in your case probably a "stock" or out of the box/factory rom.
First thing to do in your case would be to upgrade the Radio. You may well need to run the HardSPL (I needed developer edition) and then apply the radio upgrade.
From then on, its up to you which cooked rom you run as they all have advantages and disadvantages. For example, im running the Diamond TLR rom as I don't like touchflo (i think its a gimmick that slows things down - drasticaly). Using this rom i'm able to uninstall touchflo and free up significant memory. This suits me down to the ground but not those who want to use touchflo!
Take a look at the wiki (mostly) and the Rom development sub-section of this Diamond section of the forums. As long as you follow the Wiki instructions on HardSPL and then use a rom specifically for a touch diamond, you should be fine.
Be very carefull though and DOUBLE check everything, one wrong flash program and you can destroy your phone.
Have fun!
p.s. Many people think that the factory 1.37.xx roms are the most stable, even more than the later versions. I'm running a TLR based 1.37something and I am very happy with it and never have to reboot my phone.
Got it....Its all here
Hi Lats... I've tried a variety of roms on my Compact IV and I have to say, me and my colleagues at work find that Swiftblades roms are pretty much as good as they come. He's now released version 5.0 and if you're still on the original T-mobile rom, then you'll notice one hell of a difference and improvement in speed and usability.
Go for it and don't worry if your concerned about warranty, there is a stock T-mobile rom floating around on the forum and instructions on how to return your Compact IV back to it's original state.
If you find the whole rom thing confusing, then take a look at this site:- www.modmydiamond.info It'll pretty much tell you everything.
Basically though, you'll find there are 3 phases to upgrading
1) HardSPL - In laymans terms, this pretty much opens the phone up for flashing roms. Most people seem to go for and recommend using Hard-SPL 1.40 Olinex Developers Edition-Unsigned. There are consequences to using an unsigned version, it means you could in theory download and install a dodgy untested Rom, but it's up to you to go for roms on the thread from reputable guys where you can see lots of other people have installed their tried and tested roms.
Once you've done this, you'll not need to do this again.
2) The Radio - This deals with the comms side of the phone, ie phone signal strength etc etc. It's pretty much been agreed by most people that v1.00.25.05 appears to be the best of the bunch.
3) Lastly choose a rom, there are half a dozen really good roms out there and many of them are down to personal choice. Many of them are customised too much for my liking. I chose Swifts as he pretty much keeps his clean and looking like a stock rom.
You'll only have to do the Hard-SPL once and probably the radio once, unless a better radio arrives. So once you've done all this, you can keep trying different roms without the need to do the Hard-SPL and radio all over again.
Hope this clarifies things a bit for you.
Good luck and have fun!
Thanks ever so much guys. I already feel alot more confident about this. Just one question... guide suggests the following:-
Manually enter the Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time
Where is the camera button and it sounds as I need 3 hands to do this!
They're refering to the main round button below your screen in the middle of the 4 buttons, and yes you need 3 hands, but you can just about do it with 2
Let us know which ROM you upgrade to - I'm on the same ROM and radio as you are. Bit nervous about flashing the rom as my last phone (Vario II/Hermes) had to go back a month after I had it due to the screen alignment issues. After the warranty expired, I was flashing daily (lol) and yes, they do make a big difference.
I've got a copy of the UK Tmobile rom from this site, but cant remember the page now or what i typed in to get it... will try again later. It's called "RUU_Victor_TMO_UK_1.37.110.3_Radio_Signed_Diamond_52.26a.25.09_1.00.25.03_Ship"
Lats said:
Thanks ever so much guys. I already feel alot more confident about this. Just one question... guide suggests the following:-
Manually enter the Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time
Where is the camera button and it sounds as I need 3 hands to do this!
Click to expand...
Click to collapse
That is for last resort methods only...
Ensure you are connnected via activesync when doing any flashing, remembering to hard reset again after every flash,
Yeah, most definetly I will let you know but I think it will be over the weekend now. I had a quick attempt to get bootloader going, but it don't look easy. Phone just resets everytime and just reboots back to normal.
If anyone has any tips on which buttons I need to press first or if there is any easier way of doing this, I'm listening.
Lats said:
Yeah, most definetly I will let you know but I think it will be over the weekend now. I had a quick attempt to get bootloader going, but it don't look easy. Phone just resets everytime and just reboots back to normal.
If anyone has any tips on which buttons I need to press first or if there is any easier way of doing this, I'm listening.
Click to expand...
Click to collapse
If you want to flash any ROM - you dont need to manually enter boot loader to do so...
As I mentioned before.
just make sure you have active-sync running and working and the battery id over %50 charged.
I'll be doing this tonight
The Tmobile stock rom can be found here
http://forum.xda-developers.com/showthread.php?t=406327
Since upgrading to the AT&T 6.1 ROM I have 2 recurring issues. First, the device seems to have "busy" times when it will not respond to screen taps. If I turn off the phone radio the problem goes away. Second, the on/off/sleep button on the side will occasionaly turn on the phone from sleep for less than the second. The screen flashes and then back off. The next press of the button will turn the phone on.
I have seen these problems posted on other forums but not here and have not seen any solutions posted. Has anyone else seen these problems and are there any fixes?
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
The power button issue seems to be related to WM 6.1 (it's been present in every 6.1 ROM I've used). I've read several comments about it in several different threads. NotATreoFan (NATF) posted a 'workaround' in his ROM thread which has worked perfectly for me. Simply hold the power button for a very short time instead of just pushing it - .5 second works fine.
The power button issue has been revealed as a "feature" AT&T added to their 6.1 ROM. It is intended to prevent accidental powering on when the phone is in your pocket.
NotATreoFan said:
The power button issue has been revealed as a "feature" AT&T added to their 6.1 ROM. It is intended to prevent accidental powering on when the phone is in your pocket.
Click to expand...
Click to collapse
Some "Feature"
Kuschelweich said:
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
Click to expand...
Click to collapse
I had the previous stock ROM installed and whatever SPL version that was. The power switch is an interesting feature, I guess now that I know it, it makes sense. The Tilt power switch is so hard to press that it seems unnecessary.
Has anyone else experienced the lag. It is very noticable when I am playing a game like solitaire. The phone will work fine for 2 or 3 minutes then be unresponsive for 10 or 15 seconds and then be good again. I haven't installed any 3rd party apps yet, just run them from my SD card.
I gave up on the official ROM, and had to be selective on which ones to load up. My favorites were the basic naked ROMs (NATF-it will be missed, yes yes, go Phillies-That old dude sounded like a rock star, and AthineOS). Added applications (not all at once) to be able to see what programs would mess up the speed or even the sound (found out that a certain version of SRSWOW would render the volume control and anything having to do with sound as useless). Ended up with what I think is a completely functioning, lag free WinMo phone. Yes, it took a little while, but worth the effort. So far have over 35 different programs/customizations along with Igo8 and Manilla 2D (w/o Youtube or GoogleMaps) working together beautifully. To save me the trouble of having to load cabs one by one I installed SASHIMI to my storage card and, voila! Almost automated reloading of all cabs...
I've experienced the lag across some new cooked roms I've been trying. I'll have to go back and figure out the SPL situation to see if that fixes it. The lag is super annoying though.
Kuschelweich said:
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
Click to expand...
Click to collapse
Yup that was exactly my problem. I still had V1, what a huge difference, no more lag. Thank you!
TracyD follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=433835
Lev00 said:
Yup that was exactly my problem. I still had V1, what a huge difference, no more lag. Thank you!
TracyD follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=433835
Click to expand...
Click to collapse
I ran through the tutorial and updated the SPL but that did not fix the lag. I ran the unlocker and that seemed to do the trick. No more lag. I had already determined that I could stop the lag by putting the phone in flight mode. There must be a problem with the stock ATT Radio.
I no longer am having issues, thanks to everyone who offered advice.
My Tilt freezes whenever I slide out my hardware keyboard.
It does not matter what program I'm using. It doesn't matter whether or not the phone is on standby or on when I slide out the keyboard. It only happens when I slide out the keyboard. I can use the on-screen controls to go to landscape and it doesn't cause issue.
Hard resetting only temporarily fixed it. It seems to come and go. It had stopped today, for no apparent reason. Now, after having installed the RRKeyboard Fix cab, it started happening again. I uninstalled it, and the freezing stopped for about 5 minutes. Then I plugged my phone into my computer to Sync my calendar appointments, and it froze again.
Just now, I discovered that if I wait long enough my phone seems to work
correctly.
I am using the official 6.1 Tilt ROM. I have not changed my Radio, and my SPL says
"KAIS1*0 MFG
SPL-1.0.liPof
CPLD-8"
Does anyone have any ideas about fixing this?
EDIT: I just discovered that this only happens when using my phone normally. While checking my SPL information, I decided to slide out the keyboard and see if it messed anything up, I then plugged in a USB cable and it recognized it.
very weird maybe try installing teh official rom again( not hard resetting)
I thought of that, but instead decided to use this as an excuse to try a custom ROM. I am using Shifu's v10 and this issue appears to be gone. Here's hoping it stays away.
Spl! Spl! Spl!
dduuuuuuddddeeee!!! your SPL version is out of whack for your 6.1 ROM version!!! direct yourself to the wiki and the search button to see what the recommendations are regarding how to ensure matching SPL, radio, and ROM versions!!!
ASCIIker said:
dduuuuuuddddeeee!!! your SPL version is out of whack for your 6.1 ROM version!!! direct yourself to the wiki and the search button to see what the recommendations are regarding how to ensure matching SPL, radio, and ROM versions!!!
Click to expand...
Click to collapse
I don't think that's the issue, since I was using that SPL for a long time without issue. I changed to JockyW's 3.56 while installing Shifu's ROM so it's not really an issue anymore.
I imagine your problem has gone away since flashing a custom ROM, or you probably would have said something. I was wondering, however, if you had tried tweaking any Advanced Config settings (assuming you had it installed).
For instance, there's an option in Advanced config under the "Miscellaneous" category called "Enables or disables Kaiser WM6.1." I don't really know what this does, but the long description is: "Enables or disables the Kaiser WM6.1 landscape cleartype hacked (regarding D3D driver issue).
I have this disabled, especially since I'm using a 6.5 ROM, but for all I know that might help with the issue you were having.
Bob_Beard said:
I imagine your problem has gone away since flashing a custom ROM, or you probably would have said something. I was wondering, however, if you had tried tweaking any Advanced Config settings (assuming you had it installed).
For instance, there's an option in Advanced config under the "Miscellaneous" category called "Enables or disables Kaiser WM6.1." I don't really know what this does, but the long description is: "Enables or disables the Kaiser WM6.1 landscape cleartype hacked (regarding D3D driver issue).
I have this disabled, especially since I'm using a 6.5 ROM, but for all I know that might help with the issue you were having.
Click to expand...
Click to collapse
Yeah, I mentioned that the problem stopped when I started using Shifu's ROM. I thought it might have been my Kaiser Tweak settings, but after hard-resetting (and not using Kaiser Tweak, it still occured). I'm guessing some driver got corrupted.
** 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