Database Develop

Slow WinMo

After installing the new Rom's (I've tried thaihugo, saiweb and pli6128) in all of them my WinMo works very slowly if I have Vista working, and I've lots of difficulties to have 3G connection in Vista side.
As anyone experienced this also?

Take battery out for awhile after flashing

sniveri said:
Take battery out for awhile after flashing
Click to expand...
Click to collapse
Totally agree...
Needs a full reboot after flash, its sort of halfway 'tween a soft n' a hard...

I've left my Shift without battery for almost 1 hour. Still WinMo very slow when Vista is on.

motowiz said:
I've left my Shift without battery for almost 1 hour. Still WinMo very slow when Vista is on.
Click to expand...
Click to collapse
Have you loaded lots of SW on your WinMo side (limited memory on this one)...?
Have you got X-Button set to kill each app when closed..?
Are you trying to use WinMo while USBtool connected and device is Syncing (always slows the system down if you have lots of contacts/calendar entries)..?

Farsquidge said:
Have you loaded lots of SW on your WinMo side (limited memory on this one)...?
Have you got X-Button set to kill each app when closed..?
Are you trying to use WinMo while USBtool connected and device is Syncing (always slows the system down if you have lots of contacts/calendar entries)..?
Click to expand...
Click to collapse
Didn't load anything else except what comes in the rom, and configured 4 mail accounts withot attachements to save space.
X-Button configured to kill.
I don't want to use WinMo but as it is to slow I cannot have 3G connection in VISTA side.
When I start Vista the problems begin, sometimes my screen in WinMo side, becomes very strange, I reset WinMo from Vista side and get Unknown SIM status in WinMo, etc...

Flash your original ROM and test again
If it's still slow, and you still get a "crazy screen" sometimes, your hardware might be bad.
Although... if hardware is broken, mostly, these devices won't do anything at all. Strange one...
Try flashing original ROM, test again ?

lucid said:
If it's still slow, and you still get a "crazy screen" sometimes, your hardware might be bad.
Although... if hardware is broken, mostly, these devices won't do anything at all. Strange one...
Try flashing original ROM, test again ?
Click to expand...
Click to collapse
That would be great but I cannot build the original ROM. I've taken it out following pof's post but can't put it together...
Do you have the original ROM? English

motowiz said:
That would be great but I cannot build the original ROM. I've taken it out following pof's post but can't put it together...
Do you have the original ROM? English
Click to expand...
Click to collapse
OOoo!! look what I found using search!!
http://forum.xda-developers.com/showthread.php?t=424323
Its the WWE if'n ya dint know...

Problem with Tilt and Vista.

Im having a bit of an odd problem. Im running "Windows mobile device center" in Vista (64b) and when the Tilt is plugged in, something odd happens. It works normally, but its like something is constantly interrupting what im doing. About every 2 seconds! Its like something keeps "tabbing" around, interrupting what im doing. The windows flash on and off, and its just very odd. If I have a pull down menu up, it vanishes. If im trying to rename a file, it vanishes. Its like something is constantly pressing the escape key every 2 seconds. Its very frustrating, and ONLY happens when the tilt is plugged it! Has anyone had this problem on there Vista?

idk man i my phone is on it as we speak and i am as well running vista 64...hhmmm...i had a problem before with the windows mobile device center...and i went on their site and searched around and found a different version that seemed to work fine....
http://www.microsoft.com/downloads/...56-7825-43B2-AC89-2030ED98ED95&displaylang=en
thats the one i got....the once included in vista gave me some trouble so i use this one and its all good now....good luck

Well i had the same on my old pocketpc . . . .(ipaq 2210)
It seems your tilt is drawing more power from yer usb plug than it can handle.
then the usb port will be switching on/off constantly.
so disable charging over usb on your tilt, or put it on a usb hub with an external power supply for more power.
(usb delivers max 500mAh, tilt uses more when charging)
please pm me if it worked for you.
mark.

Doh. I was REALLY hopeful that the power thing would work. Sadly, not. I tried disabling charging, AND put it on a powered up, and it still happens. Gah. I will try the software next.
*edit* nope. I already had that ver installed. *sigh*.
Im going to do a windows re-install in a few weeks. I hope that will cure it. Im sure its some type of software issue.

Crap . . . .sorry to hear that.
I tried clean install too before i know upper message, and back then the new install didn't work so i hope it will work for you.
did you try clean install of your tilt?
(i have seen that a hard reset on tilt still leave some files and folders on your main memory so a hard reset isn't like a "format :c" . . . . .be sure to delete the files and folders manually before hardreset.
(even putting back a system backup leaves old files untouched on the main memory . .)
hope you can fix it . . . . .

Shift DEAD after trying to upgrade - need repair !

Bad news today :
Wanted to revert to ThaiHugo's light ROM.
Booted Windows 7, executed CustomRUU. After 1 minute, before
the real transfer of files begins, Shift BSOD in Windows 7.
No sweat, I thought, just reboot Windows 7, and hope that WinMo ROM wasn't touched yet.
However, even after removing the battery, Shift won't go to Bios, nor will it boot Vista. After power on, the HDD clicks, and that's it. If I wait long enough, the Fans will start blowing air.The power indicator is on, and the HDD led never flashes....
The WinMo part can be seen to work, albeit very rarely.
So now I'm stuck with an unbootable Windows 7, as it won't even do BIOS, and without WinMo.
Anyone else suffered from this and how did you recover ?
I'm glad it's a 2 year warranty, would have gone ballistic !

lucid said:
Bad news today :
Wanted to revert to ThaiHugo's light ROM.
Booted Windows 7, executed CustomRUU. After 1 minute, before
the real transfer of files begins, Shift BSOD in Windows 7.
No sweat, I thought, just reboot Windows 7, and hope that WinMo ROM wasn't touched yet.
However, even after removing the battery, Shift won't go to Bios, nor will it boot Vista. After power on, the HDD clicks, and that's it. If I wait long enough, the Fans will start blowing air.The power indicator is on, and the HDD led never flashes....
The WinMo part can be seen to work, albeit very rarely.
So now I'm stuck with an unbootable Windows 7, as it won't even do BIOS, and without WinMo.
Anyone else suffered from this and how did you recover ?
I'm glad it's a 2 year warranty, would have gone ballistic !
Click to expand...
Click to collapse
Did you try to downgrade to Vista and try to flash the original SnapVue?

Can't even get to the BIOS
I cannot try much anymore... device just won't boot to the bios. Only the powerled is working.
So if I take out the battery, and unpug the powercord, and wait 10 minutes, my device should at least show the bootscreen and BIOS, it doesn't.
Strangely, WinMo once in a while does fully boot, regardless the fact that the other side is "dead"
A very very peculiar problem, it seems that the BSOD while flashing a ROM has locked the EC controller and my Harddrive permanently.
I've been playing with computers for 30 years now, this one is ODD, really really ODD.
Frak, now that SD and BT will be out, my shift will be in for repairs.

lucid said:
I cannot try much anymore... device just won't boot to the bios. Only the powerled is working.
So if I take out the battery, and unpug the powercord, and wait 10 minutes, my device should at least show the bootscreen and BIOS, it doesn't.
Strangely, WinMo once in a while does fully boot, regardless the fact that the other side is "dead"
A very very peculiar problem, it seems that the BSOD while flashing a ROM has locked the EC controller and my Harddrive permanently.
I've been playing with computers for 30 years now, this one is ODD, really really ODD.
Frak, now that SD and BT will be out, my shift will be in for repairs.
Click to expand...
Click to collapse
Can you do a Fn>F10 to boot from a cd drive? If so, boot your Windows 7 from the cd to do a repair....That's what I had to do.

Need help with Incubus26Jc's Super FroYo 2.2, install issues

Hey everyone, I'm trying to upgrade from Myn's Warm Eclair [BETA 1] (I know, I know, lol I should check here more often...) to Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS10] [7/8/10] (the download link that says "DOWNLOAD RLS10" in large orange font underneath the "What Doesn't Work" secton on his 1st post.
I'm doing what I usually do to install android, which is:
download the .nbh (which is voguimg-240x320-froyo-08-07-10.nbh)
rename it to RUU_signed.nbh
place it in the ROMUpdateUtility
add the ANDBOOT folder to the root of my SD card
placing the androidinstall.tar file inside
holding the power and camera buttons to boot into the RGB 'usb' screen
then running the ROMUpdateUtility to install it and boot up the linux
in linux I hold down the center button to get the the install menu
then install both system and data to the NAND (since I don't have partitions on my 8 gig SD
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!

this happens to me all the time. the question you need to ask is "is the device getting to the desktop?" and "is the operating system fully loading to a usable state?"
in my experience answering either of these questions 'yes' puts you in a good position. there have been reports of boot sequence taking up to 20 mins. personally, i can make it to desktop in about 10 mins every time.
hope it helps.

sometimes you just need to format the sd card to fat32 again then try reinstalling after putting the files back on the card of course. if the sdcard is formatted wrong then it wont be able to read the directory and will give you that error

Darkstarrdp said:
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
It's not a problem - this is the permission setting - ignore the messages
Just let it get back to the install screen, and then hit Quit or soft-reset device.
Then wait about 10-15 minutes for first boot and go through startup setup
Reboots are quicker, maybe anywhere from 2-4 minutes.
I overclocked my vogue to 496mhz with no issues & I guess some people hit 510mhz safely.

Just to add, Ive been running at 520 for a month now without noticing any major adverse effects...Sorry to chime in

I second wisconsinated's note -- I had this problem last night. I reformatted the card as FAT32 and things went as expected after. Not sure why they tanked in the first place, but I suppose that's not important, right?

ill third that. a reformat of my microsd did the trick.

i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.

ericbond said:
i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.
Click to expand...
Click to collapse
oddly enough, with an experimental operating system, one needs to exercise extreme patience at times.
glad its all in order for you now

Thanks guys, I got it to finally install after the third try, I guess it was just having hiccups trying to install. Everything's good now.... OS installation side at least.
Now I have a different problem... my touch sensitivity is kinda out of whack.
it's like touch screen is dead half the time, on my stock sprint ROM it will work perfectly, but, on the newer builds of android (2.1's) the touch screen won't react most of the time. Like, I'll have to hit the screen over and over a few time's before it'll finally pick it up. I've used the calibration tool to get it all lined up, but when I go to test the calibration I notice that it will only recognize my touch between the .50's and .60's range, it's like it's locked into that area and won't pick up anything else. I also drew a circle around my screen about 10 times once I got it to recognize my pressure and out of the 10 circles 4 or 5 drew a line directly to the bottom right corner of the screen then it would bounce back to where I was actually pressing. It makes it really hard to get anything done on a touch phone if the screen doesn't want to pick up lol.
Like I say, when I move back to my original sprint rom everything is fine and dandy using WinMo 6.1 but who wants to use 6.1 now adays
So, is there any way to fix my touch sensitivity? or is my screen just crapping out on me?

Digitizer going bad
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)

Darkstarrdp said:
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)
Click to expand...
Click to collapse
I am not sure this can help, are you familiar with terminal?
open terminal or adb and type
Code:
cat /sys/module/tsc2003/parameters/sensitivity
to see current setting, it usually is 8192
write it down and change the param to lower value like 3072
Code:
echo "3072" > /sys/module/tsc2003/parameters/sensitivity
check the result
Code:
cat /sys/module/tsc2003/parameters/sensitivity
it should now display 3072
HTH

Really need help please

ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.

matthewjulian said:
ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
Click to expand...
Click to collapse
I haven't had this problem, but is the driver installed for when it is in the bootloader screen?
Another way you could try is flashing it from bootloader mode. Just go into bootloader mode then plug it into your comp and run the romupdate utility.

Odd
Never personally ran into it but check your USB cable. Try a different cable. Try a different USB port. I had some issues with them being a little touchy.

I dont know if anyone cares, but I figured it out. I am using a Early 2010 Model MacBook Dual Core running Parallels instead of dual-booting Win XP.
When I am in Windows XP, OSX is running in the background, when the rom update utility turns the phone off then on into the bootloader, the phone is off for that split second and parallels cant keep up with it, and the Mac trys to grab the USB connection in that split second before Win XP says "No, thats my connection", so in that split second exchange the connection with Windows and the RUU gets droped! Kind of simple once you know whats happening. No matter, I used my brother in-laws Vista Toshiba( infected with viruses to the max), it worked fine and I am now running Moonscapes 1.6 with android as well! Thank You to the people who took the time to help!! Remember guys this is a community, it doesnt work unless people respond, without participation we may as well be talking to our dogs!

You never mentioned you were doing something crazy like trying to flash your phone from a virtual machine. That never works, because the usb passthrough driver doesn't detect the windows low-level bootloader mode. How are we supposed to help you when you don't provide details?

Lol, my bad, I got sloppy!! My son dumped a Sonic drink on my dell so all I could work with was my trusty Mac, I am going to dual boot it later today. I have to say after a day with Moonscapezx's 1.6, I like WM, dont know if I like it enough to swap it out for good, I still love my Hero(at least for another 3 months when I get an upgrade, EVO!!!). Ok, well Thank You again guys, I love XDA, you guys are great