I have been having trouble with my kitchens and some strange behavior I have never seen before. So here goes and sometimes we get narrow sighted when looking for problems.
Some Basic information first:
Ervius Visual Kitchen
WM 6.5 Native kernel
WM 6.5 builds 21869 & 23071
Storage card reformated and blank.
Tried both with and without extendir
Tried both with and without modifed XIP
RunCC set to reset
Manila 2.5
All LEO packages except Dshow, Phone Canvas, SensorSDK.dll, Power, etc.
Not using OOBE setup package.
Now My problem as best as I can describe.
The best way I can describe is a startup problem. Device boots fine and goes through RunCC ok and resets. On second start when the background appears and the titlebar is shown the phone signal icon is showing no signal. The conection setup will the show up and the progress bar goes through and the say done. Sometimes it will not even go in to the connection setup. When you press done the screen does not update but you can see the title bar and the phone still shows no signal. Manila will not start it seems without a radio signal.
Now some of the weird part. Sometimes if I press around on the volume buttons and more so on the title bar and task manager it will sometime refresh and the signal pops up at 100 % signal. It is like the signal was there all along but not updated. As soon as the signal is there Manila starts to load up. One loaded all is ok.
On soft reset it is usually ok with a occasional same problem as above.
On hard reset the same problem as above is quite frequent.
Any help or ideas welcome.
I think it RunCC...
Try a different build of RunCC.
Try to use another connection setup package including ConnectionSetupDB, also check the runcc.lua, maybe you have something over there which may cause the problem during runcc.
Related
When I was using Helmi's 1.3.2 rom (I have since switched back to the latest WM2003 rom) I had some odd, seemingly hardware related, Issues:
*Back light randomly turned on and off, programs opened and closed and did random things, then the device would reboot.
*It would just randomly reboot.
*I would get a "Problem with bluetooth hardware" Error message when trying to scan for new devices some times, and I would have to soft reset.
*I could not turn off the screen in WMP while using A2DP
*The device would shut off completely and wouldn't turn back on occasionally, and the only way I could get to turn back on was to plug it in. After doing that, all the version numbers on the first boot screen would read "NONE" and I would have to soft reset the device several times to get the wireless working again.
I have taken very good care of my SX66 (I have only dropped it once), and these problems worry me...has anyone else experienced these?
I had also a lot of trouble after having installed a new version of WM5, because I forgot to wipe the memory clean (check step 9 - and especially 9.2 - in http://wiki.xda-developers.com/index.php?pagename=Helmi). Just repeating this step will solve it... it dit for me. that's another thing I won't forget anymore
I'm having big trouble with my Diamond: some time ago it started to be slower (even after many soft resets) and then some appls started fail: I wasn't able to sync via USB any more and Opera wouldn't start.
I had a US Diamond originally unlocked, with stock rom.
After unsuccessfully trying with a hard reset, I installed HardSPL and flashed the new HTC stock rom:
Diamond_HTC_SPA 2.03.412.2
Radio 1.09.25.23
Now things are much worse!!! I'm still having the same problems, but now battery life was reduced to less than 6hs in stand by mode and it gets hot! I have to go everywhere with a charger...
Activesync only connects once just after flashing. But after the first sync (at least I got all my contacts) it always says it couldn't connect or find the device.
The new Opera 9.5 also worked only once or twice. Even after a soft reset the application doesn´t completly start, it never gets past the "loading.." image (and it never showed up in the standar task manager).
I tried to install FdcSoft TaskMgr 3.1 to see if any process was consuming the CPU, but this application always hangs just after launching with the progress bar at a third.
Any help would be much appretiated.
i think you have a faulty device.. because you're saying it stays hot even after hard resets in standby?
Hi Guys,
I suppose one good thing to come out of me constantly finding my HD dead after it being on standby for a few hours (it seems intermittent) is that it seems many others are having similar issues.
Can people post their findings to the following question so we can help the community at large narrow down the issue:
When your device hangs/freezes, is it in standby or in use?
If the unit is in Standby, are you using Manila 2.5 or an earlier version?
Which WM version are you using? (6.1 of 6.5)
Have you unticked the "Today timeout" on the Today Settings screen?
My experiences are as follows:
I have only seen this since I have been using a 6.5 ROM
I have only seen this since I have been using Manila 2.5 (i think)
I install only a small number of applications
I have used both MyPhone and PIM Backup to restore info
oh and finally, it's bloody annoying!!!
If anyone has any information as to what could be causing this please post. I'm sure we'd all give our left nut to get this fixed?
This does seem to be an issue that effects some and not others, I had it happen a few times but after flashing back to an official ROM then back to custom (including SPL) I have using custom ROMs for a while now without this occuring again.
Flashmore, thanks for your input. Can you state what steps you followed for others?
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
xboxhalo said:
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
Click to expand...
Click to collapse
I'm attempting to systematically find out what the problem is by installing the same programs each flash with the exception of one. The first attempt was to move back to Manila 2.1 - so far so good but I'm expecting the same to happen at some point.
I want a good ROM, but I'm more bothered about not missing an emergency phone call because my phone is dead!
Hi all.
I'm not sure if this is actually related since when I experienced these so called "lock ups" my phone hard reset and corrupted the SD card as well. This happened two times with HD and once with Diamond2. Both phones with WM6.5.
I'm using corporate exchange and get enforced a device lock policy. I noticed that each time the device froze it was displaying the "classic" device lock number keyboard although the "default" (the new wm6.5) lock was selected.
Anyway, both phones have been working perfectly with WM6.5 and manilla 2.5 after I have started to use the ugly "classic" lock screen.
E
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
gallegus said:
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
Click to expand...
Click to collapse
That's interesting. I might try that.
I have been on Manila 2.1 for a few days and so far so good though.
I'm on WM 6.5 w/ Manila 2.1 for a couple of days and it has happened to me too.
I just tried disabling the options for turning off backlight and turning off phone. Hopefully this "fixes" the problem.
Check this thread, same subject, more details !
K
As said by Kostas66 above me. I guess this thread will soon get a lock...
As per post#10 & 11, please use this thread for future posts
Thread closed
Dear buds,
I've bought a TD2 with WinMO 6.5 lately. I had lots of bugs and fixed them all but one...
After some time from bootup (after 1 or 2 hours) the sound of phone goes off without a reason. No sound from speaker, headset or volume control buttons. However everything goes well instead sound. Phone vibrates when get call, notifications and alarms vibrate without sound etc. My only solution to get back the sounds is soft reset. After soft reset everything gets fine...
I think this is a sound driver issue but... If someone to help or show the way on forum please help (because I couldn't find same issue on search)
Thanks in advance.
If there aren't any other programs causing this by adjusting your volume levels, It may be a driver issue and you'll probably have to hard reset.
This is a common issue when flashing a new ROM without hard resetting after.
Dear Bruce,
Thanks for solution suggestion.
I hard reset three times until I bought the phone but nothing changed. I'm using the official shipped ROM and I didn't flash any other ROMs.
Extra programs list:
Klaxon
SKTools Lite
Garmin Mobile XT (Because my Copilot runs only after first installing then crashes forever)
Sportypal
Google Translator
Could that happen because of wrong flashing at factory or service etc.? I mean, this phone is a Vodafone version.
In Turkey, Vodafone signal often goes off and usually my phone gets stuck when the signal is off. Could this be the reason for unloading driver?
The digits of my phone are here:
ROM version: 2.16.468.4 (67041) WWE
ROM Date: 11.12.09
Radio Version:4.49.25.17
The fact that it works for a short while after soft reset perplexes me.
You have verified your volume is on when the sound turns off? (Sorry I have to ask this)
Any other programs running at the time is stops?
GPS software can conflict with system volume and backlight, so maybe make sure Garmin is set to dynamic settings.
Other than that, I really have no suggestions as a hard reset has not helped.
Perhaps hard reset, test for a while and see if it fails w/o any programs. Then install one prog at a time until you find the cause.
There is a slight possiblity that it was a bad flash and the driver is corrupt, which would mean reflashing the stock ROM.
Sorry I couldn't be of more assistance.
Dear Bruce
Sorry for very late answer for your last post
It's sure the phone volume is on
I've been examining the phone for one week and tried some possibilities and still no way for the bug
First I hard reseted again, then didn't install any other programs. After 6 hours, the same issue occured.
I uninstalled CoPilot (which I didn't use after hard reset) then soft reset and wait, just only some hours later, the sounds went off again.
After several soft resets, I decided to play music and monitor if it happens. Then BINGO! The sound went off just after poor GSM signal. When the phone lost the signal, it temporarily locked itself. After 2 or 3 issue, the phone sounds went off.
I think, phone starts a search after signal loss, then it tries to execute rest after 10 or 30 seconds either the signal comes back or not. After some trials it cannot reload sound .dll and sounds lock forever. But after soft reset, everything gets fine again.
To be sure about signal loss, I took the phone in flight mode for one day and wait for the same bug and the second BINGO came Phone didn't show the same bug.
After all, I reflashed the official ROM of TD2 and tried the same things but nothing changed. It's sure that the bug is not due to the wrong flashing the ROM.
For now, I'm sure that the bug occurs because of poor GSM signal of Vodafone in my region. So the question comes
Is there anything (such as a registry tweak or vice versa) to make the phone not to lock itself while loosing the signal and searching? Or do I have a way to increase the signal sensitivity?
Thanks for the worthful answers.
Regards
Guys, I have a weird issue with my X1. Im using the Energy Rom (6.5), installed a few things (including the SE Icon to replace the Windows one on the start menu), did a soft reset and everything was going ok.
After fiddling about with the phone some more, on the next soft reset i found that the Battery Icon on the taskbar would not update, see the attached screenshot, says the phone is being charged but the phone isnt even plugged to anything. Seems like it only shows the battery status of when i turn on the phone, then stays that way until windows starts again.
Any help would be appreciated,
Thanks
XtriFe said:
Guys, I have a weird issue with my X1. Im using the Energy Rom (6.5), installed a few things (including the SE Icon to replace the Windows one on the start menu), did a soft reset and everything was going ok.
After fiddling about with the phone some more, on the next soft reset i found that the Battery Icon on the taskbar would not update, see the attached screenshot, says the phone is being charged but the phone isnt even plugged to anything. Seems like it only shows the battery status of when i turn on the phone, then stays that way until windows starts again.
Any help would be appreciated,
Thanks
Click to expand...
Click to collapse
What did you install?
That usually happens to me when I install a taskbar that's missing a key .dll file. I think there's a bugfix for it in the apps/themes section, but generally when I run across this problem, I just uninstall the taskbar and install a different one with a working battery meter
harveydent said:
What did you install?
That usually happens to me when I install a taskbar that's missing a key .dll file. I think there's a bugfix for it in the apps/themes section, but generally when I run across this problem, I just uninstall the taskbar and install a different one with a working battery meter
Click to expand...
Click to collapse
Harvey is right...It's a known issue, having troubles if we install a custom Taskbar over another Icon set. Same applies when installing a custom Volume control over a custom Taskbar....
So just uninstall the Custom Taskbar...
Many thanks Harvey Dent and Xperiencer, I will do as suggested.