Database Info

upgrade without usb

Hi,
After a mounth of problem caused by my mini-usb connector, I weld it this morning. But, I cannot sync it by usb anymore. I have to sync it by bluetooth. Anyway do you think there is a possibility to upgrade it with an SD card or another solution?
I thank you.

Hi,
My first thoughts would be..
"how am I going to charge the battery",
pointless pursuing an upgrade in the circumstances?!
STI

I don't see charging being an issue, as he may very well have power even if not data running on his connector, and even if that's not the case, there's plenty standalone battery chargers on ebay. Not the perfect scenario, but grab a second battery if you don't already own one and it's suddenly way better than tossing you uni.
About the SD card ROM loading...
I've seen a few posts on it, but I reckon the SD image is always created by dumping the current loaded ROM.
So, I imagine you'll need someone else so make you an SD image of the ROM you need/want.
As for the actual dumping of the OS, I never did it, so I can't really help you there.
It's not about the uni, but here's this: http://forum.xda-developers.com/showpost.php?p=899768&postcount=8
Still, as I told you, I believe you'll need a third party to supply you with the ROM dump, and even then, be damn careful that you both have the some devices (i.e. both G3 or both G4) as it probably matters.
Take this as a hint in (what I believe is) the right direction. By no means I can guarantee that this is the only way to go about it.
Best of luck!

I have the same problem with my HTC prophet device...since i upgraded to wm6 , problem came when I activated Wm5torage
I can still charge it with my usb cable but nothing more...I`m looking to download an SD image backup from somebody
If somebody can help ...

I have the same problem, having replaced the socket it also just now charges and shows in windows as an unknown port. I have checked all the connection on the PDA motherboard and everything appears OK when measured with a meter. As windows recognises that there is a port there, it seems likely that the clock and data are available. If this is the case, it should be recognised. I can only assume that somehow the OS has become corrupt. This seems to be quite a common thing, and it would be nice if someone could throw some light on why this happens.

If the clock and data are available, meaning that the two computers can communicate, you should be able to reflash the device, since Bootloader mode circumvents the OS, and the RUU has it's own drivers for communicating with the device, evidenced by the fact that it shuts down ActiveSync to avoid interference.
Try putting the device into bootloader, then initiating a flash. If there's something, anything, wrong with the dataport, the RUU will be unable to flash. If the ROM Upload starts, the it will probably finish too without a hitch. And you'll have a new working Uni.
Also, it is not possible to flash via SD card, since the SD port can only be used with the appropirate drivers loaded, and that's done by the OS. Flashing is done while in bootloader mode, which circumvents all of the OS, and uses a separately stored on board program to access the main ROM, screen and dataport.

It is possible to flash a new Rom via the SD Card.
It does however require another device to dump the image onto the SD Card first.
Search the forum and you will find specific details on the procedure.
I believe Midget made a post about the process not so long ago.
Also could all peeps please keep these sort of issues in the upgrading section, you are more likely to get better answers there.
This forum is meant to be purely for WM6 on the Universal.
Cheers,
Beasty

Yep, here is:
http://forum.xda-developers.com/showpost.php?p=1822399&postcount=2

Whoops sorry am getting a little off topic here. Anyway boot load will not work so port is probably faulty. Got a version of WM6 on it anyway, so will use as is.

Glitches on my Wizard...

Hey guys,
I'm having troubles recently with my Wizard. I am running TNT.19199 Rom. First of all, seems tyhe touch sensors on the phone don't seem to respond as quickly anymore.
1- Also, sometimes, the volume on the phone goes dead. Which means I cannot hear the ringers and when I press the buttons. Although I can hear the conversation. At this point, I have to restart the phone to get it to work.
2- I've been having problems with bluetooth lately. Is there some sort of patch to remedey that problem?
3- Sometimes people cannot hear me clearly on the other end of the conversation...
4- I'm still trying to find the programm that turns my SD card into a virtual Hard drive for the phone. I know you guys are telling it doesn't exist but I'm not making up what I saw back in January. Maybe it has to do with a prgram called Ramldr. Anyone know how it works? Much appreciated.
Thanks guys!
Phil

heads up???
Hey guys,
I'd really appreciate a little heads up on the problems I'm having....
Thanks,
Phil

most of your glitches may be solved by a rom change. try flashing a different rom. try some other rom.
the program you may be looking for is "WM5torage". this program will turn your phone's card into a virtual flash drive on the computer. run it, and connect the phone to the pc via usb.
unless you are lookig for ramdisk which turns part of your ram into a hard drive (not very usefull as these phones dont have enough ram as is.
Bluetooth issues: just about all of the 6.1s have these issues. look for a rom that has the least ammount of bluetooth "extras" as possible.
TOUCH: touch scroling is available on just about every rom these days. most people have different sensitivity settings. you can change these settings in the registry. search the wiki.
LAST AND MOST IMPORTANT:
since your issues relate to a specific rom, keep the complaints on that thread. If you can't get help there then flash a different rom. there is a new TNT rom out here, try that one. or the slim 6.1 or any other rom that has good reviews. read the whole tread before flashing so that you can make an inteligent descision about flashing the thing or not. (I hope I don't come off rude, just trying to be helpfull)
Cphil1 said:
Hey guys,
I'm having troubles recently with my Wizard. I am running TNT.19199 Rom. First of all, seems tyhe touch sensors on the phone don't seem to respond as quickly anymore.
1- Also, sometimes, the volume on the phone goes dead. Which means I cannot hear the ringers and when I press the buttons. Although I can hear the conversation. At this point, I have to restart the phone to get it to work.
2- I've been having problems with bluetooth lately. Is there some sort of patch to remedey that problem?
3- Sometimes people cannot hear me clearly on the other end of the conversation...
4- I'm still trying to find the programm that turns my SD card into a virtual Hard drive for the phone. I know you guys are telling it doesn't exist but I'm not making up what I saw back in January. Maybe it has to do with a prgram called Ramldr. Anyone know how it works? Much appreciated.
Thanks guys!
Phil
Click to expand...
Click to collapse

About the Drive...
Thanks SVI,
But you're missing my point. I'm not looking for my ram to become hard disk space, nor am I looking to turn my phone into an external HD for my computer. I'm looking to turn my SD card into Internal HD! 4 months now and I'm still certain there is a way. Back in January when I had gotten this phone, I saw a program capable in doing that.
This is no longer a search but has turned into a quest for all those that doubt this even exists...
Anyways, I'll be looking into a rom change at this point. But I've grown really fond of tnt.19199 since it's been the most reliable rom to date!
Phil

A little more...
Okay, I'm 1 step closer...
Not totally there, but I found this info for Nokia phones. I suppose it's for symbian OS.
What this dioes is boot from MMC card which in turn gives you the liberty to load as much stuff as you want on the phone. The MMC card acts as the internal memory and not just storage card.
http://maemo.org/community/wiki/howto_easily_boot_from_mmc_card/
By the way, I read up on WM5torage. Is it possible to tweak this prgram to work in favor of the pda instead of the computer?? What if the pda read the sd card as internal memory instead of the computer attached???
Just an idea...
Phil

Not recieving SMS, can rooting fix this?

II think i have the SMS problem from the memory filling up. I don't receive any texts and I've factory reset already. I can send just not receive. If I root my phone is there anyway I can fix the setting that is messed up? I JUST put my invisible shield on and don't want to pay another $15 for a new one.

No one? Has anyone else has this problem of not receiving sms after a low memory warning?

I'm sure once a custom ROM is released, someone will have looked into that problem and fixed it in the ROM.

For now the only way to fix it is to exchange it for a new one. Rooting the phone and using the Modaco custom ROM did not fix the issue. Try to avoid using bluetooth to keep the storage memory from leaking when it gets stuck connecting. Sprint is not the best at disseminating information to it's employees so if they try to give you any problems reference one of the threads on the official Sprint forum. Will and the Sprint phone team have been able to replicate the issue with multiple phones and bricked them.
http://community.sprint.com/baw/thread/23854?tstart=0

Actually, I had the same issue when I first got my HTC Hero from Sprint. Call the actual support number. They did a walk through with me to change a system number setting. I've been able to receive text ever since. Except twitter which seems to be a Sprint global issue.

Just read this in the Sprint forum, appears it might be a workaround if you root your phone. Now if we can figure out the commands to safely delete these files, it could be done in terminal.
I think I may have found where this memory is going.
After rooting the phone, I was poking around in the /data folder and noticed a bunch of ~6.5 MB core dump files in the /data/btips directory. BTIPS appears to be a bluetooth-related service.
So I'm guessing that Bluetooth service crashes, which may be manifest partially as BT devices sitting at the "connecting..." phase, are generating core dumps that are left on internal memory and shouldn't be.
I deleted all of these files (all named core.xxxx where xxxx is a string of numbers), rebooted, and reclaimed almost 70 MB of internal memory. You do have to root your device in order to delete these files, though.
The HTC devs already know this, as wengla indicates, but it might help the few of you experiencing this problem with a rooted phone.

I've already hard rest the phone so no files anymore, but whatever flag is set is permently set. I don't get how, especially after a hard factory reset. So as long as no one knows what that is even rooting won't help me. I am getting a new phone but it ticks me off especially since I just installed an invisible shield on it.

[Q] Need help tracking down resource leak in WM6

At least I think it must be a resource leak. I have multiple WM6 devices that all behave the same way when my application is run. After a while, maybe 15 hours, they gradually deteriorate and refuse to start other applications. At first, it will just be an application like Opera that will not start. Eventually, things like File Explorer will also not start. When I say they won't start, I mean that I get the "not signed with a trusted certificate or one of its components cannot be found" message.
My first thought was that there was a memory leak, but according to the output of GlobalMemoryStatus, the system's memory use is not increasing over time. Then I thought that it might be storage space since I'm generating a big log file. But the storage space still sits above 60MB when this happens.
Restarting the device gets everything back to normal. So far, this is what I know:
1. I'm using the RIL. I noticed today that after about 12 hours, I stop getting RIL notifications.
2. I'm monitoring memory with GlobalMemoryStatus, but the available physical memory doesn't seem to be decreasing over time
3. The thread count remains constant for the life of the application
4. My storage space is decreasing, but there is still over 60MB available when everything starts to go wrong
5. In the end, the device winds up with the screen lock on, even though it is not configured.
It seems that there must be some kind of resource leak. The only other thing I can think of are kernel resources. I tried to rule out things like event handles through static code inspection, but maybe there's something I'm missing.
Does anyone have any suggestions as to how I would troubleshoot this further? I'm using VS2008 and a Tilt2 and an HTC Imagio (it happens on other devices as well).

I tracked this down to a registry handle leak. What bothers me is that I had to do it by static code inspection. I just looked for things like CreateEvent, RegOpenKeyEx, etc.
Since this didn't seem to show up as consumed physical memory, does anyone have any methods for inspecting kernel resource consumption on Windows Mobile? Do I have to rely on KITL and Platform Builder with the emulator? I'm hoping that there's some way I diagnose this kind of problem with a real device. From my perspective, the device just started to fail and there were no external indicators to warn me of the impending failure.

sbaker25 said:
I tracked this down to a registry handle leak. What bothers me is that I had to do it by static code inspection. I just looked for things like CreateEvent, RegOpenKeyEx, etc.
Since this didn't seem to show up as consumed physical memory, does anyone have any methods for inspecting kernel resource consumption on Windows Mobile? Do I have to rely on KITL and Platform Builder with the emulator? I'm hoping that there's some way I diagnose this kind of problem with a real device. From my perspective, the device just started to fail and there were no external indicators to warn me of the impending failure.
Click to expand...
Click to collapse
hi!can somebody to help me?
i have asus p535 and i reset "start""settings"default settings"and i lost all from device.after apear align screen and remain like this
i think i have to install window mobile.can you tell me step by step how?
10000 thanks

Sorry, accidental re-post. Don't think I can delete it altogether...

Observations as to why market breaks / force close, and other anomolies

As I suspected early on the issues boil down to corruption within the User Data or Cache partitions, less often on the system partition due to an unexpected shutdown of the device. Shut on these devices need to follow the proper shutdown routine as any linux environment. Following this best practice will ensure that all data is written out to its corresponding file system by flushing all cache, unmounting the file system, etc..
Here are the culprits of why we see so frequent random Force Closes, Market Resetting, etc. ultimately resulting in an unclean shutdown, corrupting some data.
1. The button we use is also a forced off button. Typically if you hold it down too long you are powering off the device.
2. Some times when in sleep mode you see the Viewsonic logo upon starting - that means that the system shutdown (most likely crashed).
3. If your running Vegan your hitting the reboot.. I dont know for sure but I suspect this is NOT performing a clean shutdown... (I dont have a copy of the source)
Anyway... wanted to pass this on... as last night my data partition became corrupt after using the Reboot function on the Poweroff menu of Vega 5.1..

shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing

My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.

roebeet said:
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
Click to expand...
Click to collapse
I have been on stock since I got the device just moving to the newer versions when they come as OTAs and have never ever had to mess with my partition, so I don't THINK the issue is in the stock software. In fact, the only problems I've ever encountered were when I used the enhancement pack, in which case my screen started to become unresponsive and the calibration.ini I was told to try did not work. Since then I went back to 3389 and the device has been perfect ever since.
I could be wrong though and just very, very lucky....here's to hoping. Another thing to consider is maybe the memory is going bonkers for some reason. I've had flash memory that lasted forever and I've had flash memory that has gone wacky over a period of 6 months....even a wipe by the utility designed to do it doesn't fix it properly. I don't know how CWM wipes or partitions the memory, I do know there's supposed to be a special way to do it.
If it's not faulty memory off the bat, then that leaves something in the 'extras' being put into these ROMs. Maybe some of the newer tegra drivers or some coding to make the ROMs faster - I'm just saying, can't leave any stone unturned.
Has anyone that has stayed loyal to stock encountered these issues? We have to ask that question I think. Then we ask how many of the people playing with ROMs are seeing the issues, this would include people that have used CWM to partition and mess with their mounts initially.
I can say I've never seen data disappear from my internal memory or my SD and I can also say I've never seen multiple FCs except after putting in the enh. pack (keep in mind I got my tab on Dec 20something, so I had 3053 and then 3389 soon after).
The first sign of anything being 'corrupted' on it's own at stock and I'll be sending mine back. As an owner of Android since Android's been around, I've never had my G1 or MT4G (or any smartphone before it) become corrupted due to not being shutdown or reboot properly and while this is a tablet I think the fundamentals should be the same. Pampering 'faulty' memory is a risk. You can wipe and re-do all you want, but if it's faulty it's going to stay that way.

Ive done that but I guess you can say unfortunately I have had only clean shutdowns since then... The last corruption I had I formatted my data and cache partitions before I ran logcat.... Of course thought of that afterward....
Generally if any has FCs, etc. etc. run a logcat and post it here... we will be able to confirm this...
We could change the way the partitions are created and add a sync which will further reduce chances BUT will take a performance hit...
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I reviewed the out of the box framework source on the google GIT and technically if a reboot command is given a clean shutdown is performed via the framework... but the widget on the shutdown screen I suspect is not calling the method properly or is not being called at all... All speculation at this point... But for sure there is corruption occurring..
Since the last corruption I switch over to pershoots kernel... Even though his kernel seems to be a little slower he seems to have included the latest drivers which other items relate to data integrity (im reading into the release notes).
NEO: The first thing I did when I got my device install CW, Vegan... Updated Kernels also... Never had an issue until the first time (yes about a day ago) I used the reboot feature of Vegan. That corrupted my user data. I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
But again.. between the wrongly placed power switch, the unprovoked reboots (ie viewsonic screen showing when trying to wake up the device) and the reboot button possibly not performing a proper shutdown will sure increase the chances in a wider distribution of users. So it may not be a CW issue and just some poor design.
When I have time today I will verify if the reboot function performs a clean shutdown... if anyone has the time please post the logcat... Im going to be running around today and will try to get to it..
watson540 said:
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
Click to expand...
Click to collapse

stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
Click to expand...
Click to collapse
AFAIK they're running yaffs ATM. Next move is to ext4...
Read some articles about this several weeks ago, apparently many apps do not properly flush file caches. One of the articles was a Google developer post about file corruption along with their API method which did a cache flush prior to a close, then a bit later was the Google indication that they were planning to move to ext4 FS to further help alleviate the problem.

stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
Click to expand...
Click to collapse
That's my point. How many times since we've had our Android and smart phones have we had situations where they are turned off or rebooted without the proper procedures? Power drains till they die, they drop and reboot, we clog them up with stuff or some app drives them nuts and they reboot or shut off....Yet you rarely if ever hear about a phone's data being 'corrupted' with stock software. Sure it may happen with official OTAs etc, but never just off-the-bat like what's happening with the G-Tab. But it's not happening to everyone either so I'm just looking to see if there's a pattern.
Even since the G1 and newer phones, you don't really hear about or see file corruption issues on stock software with these phones. It's when users start going to ROMs that you hear of issues cropping up. That's not to say it doesn't happen at all at stock, I just think we're seeing it in a more concentrated fashion here because of all the formatting, re-partitioning, etc. At first you hear, 4GB is a great partition size, then you hear there are problems so move to 2048, then you hear 256MB swap, then no swap since Android doesn't use it. Then dataloop for speed, then no dataloop because of critical issues. Rules and instructions change almost on a daily basis. I think it's more than these poor flash drives can take I find sometimes it's good to keep it simple.
I owned a Vibrant for a while...decided it was a PoS when at stock I was seeing bad lag (because of Sam's terrible FS). People said...do the speedhack, it'll be fast!, but what was the caveat? Having to reboot the phone almost weekly, sometimes several times a week, and people were seeing what? Data corruption. That's not for me. Give me something that is lag free (doesn't have to be a bullet train, just don't skip on video or audio and make sure my live wallpaper and drawer animation is fluid and I'm happy!). Point being....keeping it simple may help to alleviate some of the issues. If people are seeing these problems with stock, then you're absolutely right and it would be a point of contention that the failsafe isn't working right.
Otherwise it seems the stock OS on these things are able to self correct in most situations and it may just be some of the many tweaked features in these ROMs doing something it shouldn't - or, I may just be very lucky indeed.
I'm still dying to get the OTA - I haven't seen one since 3899 yet.