Database Develop

BatteryStatus annoying prompt

for some reason i have been getting a prompt about every few hours that says
"BatteryStatus Today-Plugin"
"this is shareware and you can use it "as is" and as long as you want!
thank you for using BatteryStatus Advanced!"
i have Open Touch v3.0 Biggy WM 6.1 that was just flashed last week w/no problems (only this little one).
any one have a solution for this?
thanks
DK

I have the same exact issue, it just started this morning. It used to do it before, too, and it took another flashing to get rid of it. It looks like the cook used an incorrect version of BatteryStatus.
From the BatteryStatus Author's site:
I have a nag-window sometimes. How can i remove that?
A registration system is currently in testing state. If you want a nag-free version (for a while) you need to register at xda-developers and use one of the versions provided there.
:'(

so where does this leave us
orochidp said:
I have the same exact issue, it just started this morning. It used to do it before, too, and it took another flashing to get rid of it. It looks like the cook used an incorrect version of BatteryStatus.
From the BatteryStatus Author's site:
I have a nag-window sometimes. How can i remove that?
A registration system is currently in testing state. If you want a nag-free version (for a while) you need to register at xda-developers and use one of the versions provided there.
:'(
Click to expand...
Click to collapse
alright, its not just me. so what now? i really don't want to flash again. i am already registered here, so how do i get/install an "xda version"?
let me know if you have any ideas.

I just installed the BatteryStatusExt.1.05.UPXed.build_0290.CAB from this thread:
http://forum.xda-developers.com/showthread.php?t=270751
So far it seems like my issue has been fixed. I hope it works for you, too.

I had the pop up since this morning too. I did a soft reset, and since then there hasn't been a prompt yet

thanks for the searching
orochidp said:
I just installed the BatteryStatusExt.1.05.UPXed.build_0290.CAB from this thread:
http://forum.xda-developers.com/showthread.php?t=270751
So far it seems like my issue has been fixed. I hope it works for you, too.
Click to expand...
Click to collapse
I followed the thread and it says on the first paragraph that the BatteryStatusExt.1.05.UPXed.build_0290.CAB could damage your device.
this has me skeeved out. i might just give it a day or two, and if it continues, i'll just flash to Open Touch v4.0 Biggy. i just got this phone a month ago and i don't want to kill it yet. thanks for the suggestion
DK

hmmmmm
Jerommeke said:
I had the pop up since this morning too. I did a soft reset, and since then there hasn't been a prompt yet
Click to expand...
Click to collapse
i wonder if this is a coincidence? i bet that this pop up is scheduled at the end of every month or something like that.

digitalknoll said:
I followed the thread and it says on the first paragraph that the BatteryStatusExt.1.05.UPXed.build_0290.CAB could damage your device.
this has me skeeved out. i might just give it a day or two, and if it continues, i'll just flash to Open Touch v4.0 Biggy. i just got this phone a month ago and i don't want to kill it yet. thanks for the suggestion
DK
Click to expand...
Click to collapse
EVERY version of BatteryStatus can hurt your device if you use it incorrectly. For example, overclocking to above 260 is not smart and will shorten the life of your device. It could just freeze up and stop altogether. It's nothing specific to that version, just that overclocking in general is pretty risky stuff if you push it.

i did not know that...
orochidp said:
EVERY version of BatteryStatus can hurt your device if you use it incorrectly. For example, overclocking to above 260 is not smart and will shorten the life of your device. It could just freeze up and stop altogether. It's nothing specific to that version, just that overclocking in general is pretty risky stuff if you push it.
Click to expand...
Click to collapse
cool, well thanks for that info. i have seen a lot of people clocked at 247 and up, and i tried that, but i swear the back of my phone was getting hot. i switched it over to 234, and it runs just fine for me. i don't think i would be able to tell the difference anyway. great, then i will open that cab up and see what happens. thanks for the info orochidp.
DK

Jerommeke said:
I had the pop up since this morning too. I did a soft reset, and since then there hasn't been a prompt yet
Click to expand...
Click to collapse
This pop-up is incredibly annoying.

i hate the latest version and this still pops up. how do i fix please?
I soft reset and it still no work.
Thanks

Low memory error after new ROM flashes

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).

another bricking question

My unbranded TyTnII took a dump today, and reset itself to OEM condition, not so bad, except the data base was corrupt, so I would not configure a connection to my carrier (T-mo) .
So, I took it home, hooked it up to activeSynch, and brought up a previous sprite backup file to restore it.
Now it's a paperweight- it will start, display the three three install lines R-G-D with the Smart mobility splash, and that's it. I can't get it into bootloader, or anything else for that matter. Any ideas?

ttruex said:
My unbranded TyTnII took a dump today, and reset itself to OEM condition, not so bad, except the data base was corrupt, so I would not configure a connection to my carrier (T-mo) .
So, I took it home, hooked it up to activeSynch, and brought up a previous sprite backup file to restore it.
Now it's a paperweight- it will start, display the three three install lines R-G-D with the Smart mobility splash, and that's it. I can't get it into bootloader, or anything else for that matter. Any ideas?
Click to expand...
Click to collapse
If you get to the 3 color screen you are in bootloader my friend, do you notice the USB sign display in the screen? If you get that you can flash. I will recommend that you hard spl your device first (Please read the sitcky of how to perfom it, click under my TyTNII link)

Moved as not ROM Development..
Hard-Reset and do not use your backup as may be corrupted...
If that does not work then try and get into bootloader i know you said you can't but try again and flash stock ROM.

thanks for the move, and my apologies for the mispost- I realized only afterward I had put this up in developers.
I can't get to bootlogger mode- the phone hangs at the initial splash where it displays the SW versions of R D G. It will not move past this.
I hold the camera and on buttons, and push and hold the reset pin, but this is as far as it gets. I will sit here, so far for an hour, but will not progress further.
What am I missing? It's been some time since I've had to muck with it at all, so I've become unfamiliar with the tricks.

It's not bricked as long as you can get meaningful info on the screen. It sounds like you need to revisit HardSPL and put on a newer version. Then flash an appropriate rom.

All right,
Many thanks for the help! I flashed and manged to get the bone stock HTC WM 6.0 ROM loaded.
Now, at the risk of asking what could be considered a dangerous question (almost as bad as starting an oil thread on a moto list) what would be considered the latest and greatest ROM of them all? these days? I haven't been on this forum for quite some time, and I'm sure you all have been busy w/updates. I gave up when WM 6.1 came out, screwed up the GPS settings and made the camera even worse, so I've just stuck with my plain 'ol HTC OEM ROM.
Any suggestions?

ttruex said:
All right,
Many thanks for the help! I flashed and manged to get the bone stock HTC WM 6.0 ROM loaded.
Now, at the risk of asking what could be considered a dangerous question (almost as bad as starting an oil thread on a moto list) what would be considered the latest and greatest ROM of them all? these days? I haven't been on this forum for quite some time, and I'm sure you all have been busy w/updates. I gave up when WM 6.1 came out, screwed up the GPS settings and made the camera even worse, so I've just stuck with my plain 'ol HTC OEM ROM.
Any suggestions?
Click to expand...
Click to collapse
Yes, try them all and pick which one can meet your daily needs

having tried quite a few 'light and fast' types, i would say stick to more or less standard 6.1.
i spent a lot of time looking for cabs and then adding back in all the removed stuff i needed.
then get spb mobile shell on there and have a good looking phone.
6.5 never worked properly, esp messages, but a few other obscure probs.
my 2c

Sleep of Death" on (almost) every recent custom & stock ROM

Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Edit: confirmed solution method described in post# 10 http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10 . Thank you agent 47 big time for the tool you provided!

Ibster said:
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Click to expand...
Click to collapse
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?

MCbrian said:
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
Click to expand...
Click to collapse
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.

Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also experience it on my Tilt 2 AT&T unlocked, so i reverted back to Sense 2.1 Euro 1.86.401.0. any solution there, i bought mine from Negrielectronics USA.

Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also exprence it on my Tilt 2. is there any help out there

It's because chiefs have updated their XIP. Ask them to cook a rom for you with the old XIP from stock HTC WM6.5 Sense 2.1 rom.
Ach, that's just my theory based on my experience. I might be wrong, so keep that in mind.

I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6

Same here on the SMS black screen
ctbear said:
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Click to expand...
Click to collapse
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.

Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
Yes....interesting that I've never had this issue on Energy's...my guess is he doesn't cook in the latest HTC SMS client which can be unstable at times
Are you talking about Elcondor's GTX theme? Yes that is a very awesome theme
I couldn't wait until 201x version comes out so I made my own Not as good as GTX but I'm half satisfied now

Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
like i mentioned in the the post#1 I had these problems with almost all recent (last two weeks) custom ROM releases, ROMs of different chefs. Because others or the majority of people don't have any problems with that I thought the reason must be hardware issues. yesterday I saw this thread http://forum.xda-developers.com/showthread.php?t=649191 opened by agent_47 where he provides a modified tool:
agent_47 said:
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
Well I used it and have flashed to Sergio's Leo Cell Evo 6 and I can confirm that I haven't had any "sleep of death" issues, well still haven't and hope I won't have this "SOD" issue anymore. And when I tried this same ROM before I wasn't even able to make a proper configuration and set up the phone because the phone always froze or as soon the screen went off I wasn't able to activate it back without soft reset.
So maybe this is a solution and could help others who also are having this issue of "sleep of death".
Please if you try the tool from the mentioned agent_47's thread, let know us here because it will be very useful for the rest of the users to finally figure out "the dark side" of their phone and fix it.
Cheers, Ibster

Solution
I had this just recently. Funny side was that I installed an official new ROM from HTC which I just updated. Somehow the phone just didn't want to turn on and show the screen. So just like you guys said, hard-reset did the thing but just when the screen went off, same thing happened.
So what I did was wipe/clean or any other name. Practically did the installation of the rom again. Now, the device works normally and without any problems.
Maybe this happens because some old files of older ROMS sayed on the device itself and started making problems. Anyways, check this thread too, maybe it will explain something more: http://forum.xda-developers.com/showthread.php?t=649191
Or, final explanation. Our Rhodiums have soul inside their little chips and they just simply fu.k with us They tell us they're too tired of so many ROM changes.

I have also had this problem with my two latest official swedish roms (manilla 2.1 and 2.5) cant remember if I had it when I used 6.1. Now I use a cooked rom and still have the issue several times a week. The only thing I had done with my Rhodium before using cooked Rom was flashing hard spl for future use. If its not an inbuilt hardware/software problem from the beginning the only thing I can point at in my case is hard spl?

Originally Posted by agent_47
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
back with my kaiser you always had to flash back to stock before going to a new ROM no matter what, for just this very reason...
could flashing back to stock be a 'best practice' that we as users should start doing to help with this issue?

I - have had some xperience with the issue in a few ROMS. Im a loyal flasher of Agent 47s masterpieces. And a month or so ago he had like 2 or 3 builds that had this issue. From what I remember he said that he thought it had to do with some sys evrybody was using to cook roms. and after her came out with this diagnosis and "fixed"(i dont know the technical part of what was fixed) this problem it has never happened since. But a good thing I would say to try is in Agents thread about 4 or so pages from the last page(maybe more or less) but close to the last page he posted a .zip file for this mitty fix. and you essentially flash this zip just like a rom then reflash which ever rom you had or a new one and ta da. Ive also heard of people reflashing a stock rom with results from doing so but from what Agent said is flashing a stock rom then back technicaly "shouldnt" do anything and to definately use mitty. But one of the other frequent valkyrie users that I chat with all the time Mcbrian who posted here on the first page has used the stock rom and did have whatever issue he had cured dont remember what that was tho.
UPDATE- Oh I guess that Agent has a thread for Tool29 so you dont have to search through his thread to find it.

I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.

aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
Great! I'm glad to hear your confirmation. I now on my side haven't had a sleep of death for three days on the ROM (Cell Leo V6) that previously, before I used the agent_47's tool, couldn't even start normally at all or had extremely many "sleeps of death". But I also noticed overall improvements even though the speed slows down but there are barely any freezes and stability is much better.
Cheers, Ibster

aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks

kienkham said:
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
Click to expand...
Click to collapse
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.

Ibster said:
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Click to expand...
Click to collapse
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks

kienkham said:
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
Click to expand...
Click to collapse
Your steps should be
1. Shutdown tp2..
2. Remove memory card( I also removed sim card).
3. Turn on tp2, connect through the computer through active sync.
4. Run task 29. Let it load flash, whatever it is doing until it actually reboots.
5. At this point, everything should be cleaned, you don't have a rom or radio anymore, so its blank, so you "pull battery out."
6. Put memory card/sim card back in. Flash radio through boot whatever menu. Soft reset it yourself. Pull battery out again.
7. Flash rom this time, and soft reset it again. Now rom should start setting up.
This shouldn't be rocket science.

X1 random freezing issue

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