Database Develop

sms taking 5 mins to open!! PLZ HELP

Ive been having some problems with my tmo wing lately in terms of extreem lagging. Ever since I have used pocket mechanic to defrag my storage card, everything went to sh1t on my phone. I cant boot my phone with my storage card in the slot or it will just reset when it gets to the green windows mobile background. And most importantly, whenever I open "Messages" on my phone, it takes honestly 5 or more minutes to open, then another 5 to open sms/mms then another 5 mins to open/reply to a sms. My program memory is usualy always ATLEAST over 10MB and I had batery status running and while i was opening these windows at the task bar it showed it was using 0% or minimal processor usage, so im assuming that it's not executing properly... does someone have a fix for this? can someone help me out? because to temporarely fix the issue i have to reboot the phone... thanks!
- Norman

Here's something you should try.
Remove the card then insert it into a card reader at your computer. Copy everything on it and then format the card using FAT16.
Now back-up everything possible on the phone. (in your case this could take a while). Place the back-up file on the computer, if you use the card for back-up reformat it again after you complete the process. Then hard reset the phone and check to see if it still has this problem. Place the empty card inside the phone and try to copy some stuff to it. If everything is ok, restore your files using that back-up you just made. Check to see if the problem manifests now. If it does, clearly there is something rong with your program configuration and you may want to reinstall all your programs manually.
If the phone still runs slow after a master reset you should try to rewrite the phone's ROM as a last resort option. (your back-up copy woun't work after this). If it still runs slow even after this, then... well that's bad. It's something I call "the dead slow card problem". I've tried to find a fix for this for about 3 years on different htc products, but with no succes. The good part is that there's a very small chance this can happen in the normal every day usage. Try this things first and tell me what happens.

wow... Before i even attempt this surgery, i just want to say thank you very much for taking the time to write all this. it's very appreciated.
Before i try all this, i got a few Qs.
What do i use to back up my stuff on my device? or do i just copy paste important stuff... if so what about extensions and associated files...
And what involves a hard reset? does it effect the registry tweaks that i have done? in the end... what will be reset?
- Norman

I really appreciate ur help! ive done as u said and everything seems fine now... my phone is now back to scratch, which im happy with so I can start fresh and avoid all that junk I had on before... THANKS FOR UR HELP! UVE BEEN GREAT! A+
- Norman

More Collateral Damage

Hi everyone! I got my Wing like 2 months ago, and I did what every newbie does. I Installed lots of things just to realize that I would use 10% of the stuff. Then, started the cleanup,trying not to hard reset it, just as a matter of pride.
The worst thing I did to my Wing was Pocket Mechanic Pro. It's famous "registry optimizer" swept away my voice command among other things. After some research, and ivanmmj's inspiration (thanks again, ivan), I managed to fix almost every issue that PMP's registry optimizer caused. The only one remaining is that everytime I soft reset the phone, it keeps looping and never gets into today screen. T.Mobile logo and silly music, Windows mobile logo, and then after a while, starts all over again, and again, and again. The only workaround for this is to take the microSD out and when I see the today screen reinsert it. No big deal, but sometimes it's recognized as Storage Card 2 so I have to rename Storage Card and reinsert the microSD. Any ideas on what might be causing the restart loop?? Help would be really apreciated....

A thing may be you have missing registry keys and the OS identifies bad paths. Sometimes it happens with *folders* called "Storage Card" and then you must rename the SD card. (This happens usually if using software for english-only systems and you're using i.e. spanish WM which calls "Tarjeta de Almacenamiento" to the SD card, then you may fins sometimes a "Storage Card" as a folder, not the SD card).
Another *different* thing (I think that's not happening to you now) is the SD card is bad, and you must format it. Sometimes the device freezes without any apparent cause...
Well, I posted to your other thread about your problem, Ivan suggested you to hard-reset (I hard-resetted many many times my Herald... I'm a newbee forever ) and the best you can do is:
1) Search for a good ROM, do *every* previous step (including a search and download of your original ROM and Radio, etc.), and then install this ROM you prefer. A Light or Naked will help you to have an empty device to fill it at your own wish.
2) Look for an app which does backups, and backup your registry.
3) Look for an app which helps you to enter "safemode" if any problem appears. With Monocube v.2 you can align screen and enter to something similar to standard mode, with Monocube v.3 you can't but you'll be able to solve problems (those apps are not free)
4) Install Schap's Advanced config, and config your device (take care of configuring options for the Herald/Wing, not for the Kaiser or others)
5) Install on the device ONLY the apps you'll or your device will need. the rest, you'll have enough space for them in the SD card.
6) Try to minimize the use of RAM, so that you must have the fewest apps running.
7) Backup all your device again so you'll be able to recover your config without spending looots of days installing again.
8) If something wrong happens, you'll be able to boot in safe mode and correct it or to hard-reset and recover your old conbfig/installation.

how to troubleshoot random freezes and restarts

Hi guys, I have had a G1 for over a year now, and it has been rooted for that long. I began using cyanogen's mods since 4.1 or so, and they have been rock solid until recently, when I upgraded from 4.2.6 to 4.2.7. Ever since that upgrade, my phone has been "freezing" and rebooting at seemingly random intervals.
First, let me try to define what I mean by freezing: this usually occurs when the phone is put to sleep, and it just refuses to wake up. The screen remains black, however my notification LEDs continue to flash (if they were flashing before). Sometimes, the phone freezes while I am using it; buttons stop responding, and opening/closing the keyboard does not change orientation. The phone usually gradually slows down to a crawl before this type of display-on freeze happens. In both cases, I am able to restart the phone by pressing call+end+menu buttons.
For the restarts: these started happening recently, I'll guess after 4.2.9. This always happen while I am using the phone. It'll pause for a second, like it's frozen, then restart back to the G1 boot screen a few seconds later.
I have tried wiping, repartitioning my SD card from scratch, using the phone without any of my apps installed, etc. The only thing that seems to fix this is if I downgrade back to 4.2.6. I have tried to narrow this down to the best of my ability, but I still cannot figure out the cause. My question is, how can I begin to troubleshoot this? Is there a log or some way for me to see what is the last thing the phone tried to do before it froze/rebooted? Right now, I don't even know where to begin.

well for the phone freezing it MIGHT be too many apps running in the background and eating up CPU usage...download advanced task killer from the market, it allows you to close apps that run in the background.
as for the random reboots, i am almost certain it has to do with the rom you are on. there should be an app called "log collecter" in your app tray, it comes with the rom, try and get the logcat from it when your phone reboots, and send that logcat to cyanogen via the link he provides on his thread.

2 things that I can think about:
1. Wipe you dalvik-cache
if that does not fix it
2. This may be a good time to re-format the ext 2/3/4 partition of your card and do a complete wipe.

I have this exact problem, it first started with random sd card errors "removed sd card" with an sd card inserted, and now the black screen of death, I reformatted and repartitioned my 8gb transcend class 6 card and flashed latest cyanogen. Today I got the black screen again so I used nandroid and went back to cyan 4.0.4, I still got the black screen freeze running old rom but so far sd card is working so not sure what the cause is, bad sd card? I just got this card a month ago... or phone going bad?

yeah, i get the freeze, its usually when i am running multiple resource eating apps. Try advanced task killer for a convenient notification bar click away from closing apps.
I also get the other problem where it wont wake up! Seems like we are running into the same problems under the same ROM. When it doesnt wake up i usually wait a few seconds and try pressing other buttons than the menu button to wake it up when its not turning on. A combination of waiting 5 seconds and trying a different button usually wakes it up.

Hey guys, thanks for the logcat info.
The most frustrating part about this problem is that it is unpredictable; it just happens when it feel like it and is impossible for me to reproduce, therefore I cannot figure out the cause nor can I tell whether or not any changes I make have any effect.
I do have ATK, and I use it regularly. It still doesn't stop this from happening. In fact, I installed ATK in order to try to solve this, which means before this started occuring, I did not even have ATK installed nor did I have this problem.
Can anyone tell if there were any significant changes from cyanogens 4.2.6 to 4.2.7? I see the changelogs, but most of it doesn't really mean anything to me because I don't understand what its talking about.

Yeah I usually get the freeze after installing a new rom onto my htc dream 32a. I just take out the battery and put it back in. Then I reboot and have no problems after that.

try going back to previous rom you had and see if the problem still exists... could possibly be an issue with latest update for rom...

Booting with Removed SD wreaking havoc. Need help.

I seem to have done some real damage to my phone and I could definitely use the help of fellow XDA'ers. I took my memory card out to put some files on my PC. Phone was off so no problems. I reinsert the SD card and reboot. Now although I'm absolutely sure the card was fully inserted, once the phone fully booted I had the "SD Card removed" icon in the corner and everything started to force close. So I quickly shut the phone off, made sure the card was fully in, and rebooted again. it loaded up again, and while the no SD Card removed error was gone, I was still getting FC's left and right and apparently have no gps, no wifi, and no 3g. So I once again rebooted into recovery, ran the fix permissions and rebooted. Again, booted up and FC's everywhere. So now about 90% of my apps FC on launch (either actual launch of the phone or by pressing the icon), I can't activate WiFi or GPS, and I have no data/3g. What happened and how can I fix this? Thank you so much in advance for your help.
Edit: After a little more fiddling, I find that I can't change any settings. I can't set screen timeout, notification levels, so on and so forth. What happened?

FatBoyExtraordinaire said:
I seem to have done some real damage to my phone and I could definitely use the help of fellow XDA'ers. I took my memory card out to put some files on my PC. Phone was off so no problems. I reinsert the SD card and reboot. Now although I'm absolutely sure the card was fully inserted, once the phone fully booted I had the "SD Card removed" icon in the corner and everything started to force close. So I quickly shut the phone off, made sure the card was fully in, and rebooted again. it loaded up again, and while the no SD Card removed error was gone, I was still getting FC's left and right and apparently have no gps, no wifi, and no 3g. So I once again rebooted into recovery, ran the fix permissions and rebooted. Again, booted up and FC's everywhere. So now about 90% of my apps FC on launch (either actual launch of the phone or by pressing the icon), I can't activate WiFi or GPS, and I have no data/3g. What happened and how can I fix this? Thank you so much in advance for your help.
Edit: After a little more fiddling, I find that I can't change any settings. I can't set screen timeout, notification levels, so on and so forth. What happened?
Click to expand...
Click to collapse
Tried repairing ext file systems?

FatBoyExtraordinaire said:
I seem to have done some real damage to my phone and I could definitely use the help of fellow XDA'ers. I took my memory card out to put some files on my PC.
Click to expand...
Click to collapse
Windoze no doubt. Windoze is HOSTILE to non-MS filesystems and WILL attempt to destroy them.
Other possibility is that you simply didn't click the card in all the way.
Anyways, what has happened is that your phone booted up and was missing a ton of applications that it was expecting. It therefore irreparably destroyed your package configuration.
You MIGHT be able to salvage it if you have a recent backup of the file /data/system/packages.xml.
Try restoring that file, syncing the filesystem, and rebooting via 3-finger-salute INTO RECOVERY ***IMMEDIATELY*** after syncing. Then do a fix permissions and reboot normally.
... and cross your fingers.

r3s-rt said:
Tried repairing ext file systems?
Click to expand...
Click to collapse
I did that, but it was a no go. Everything still FC'd, couldn't change any setings, and it says my phone doesn't have internet permission, so anything requiring data access doesn't work.
lbcoder said:
Windoze no doubt. Windoze is HOSTILE to non-MS filesystems and WILL attempt to destroy them.
Other possibility is that you simply didn't click the card in all the way.
Anyways, what has happened is that your phone booted up and was missing a ton of applications that it was expecting. It therefore irreparably destroyed your package configuration.
You MIGHT be able to salvage it if you have a recent backup of the file /data/system/packages.xml.
Try restoring that file, syncing the filesystem, and rebooting via 3-finger-salute INTO RECOVERY ***IMMEDIATELY*** after syncing. Then do a fix permissions and reboot normally.
... and cross your fingers.
Click to expand...
Click to collapse
I'm guessing I didn't click it all the way in because I have done this 100's of times before and it never happened. Unfortunately, I don't have a recent back up of that file so it's sounding like i am screwed. Would i be able to just wipe the phone, the ext, the cache and start over from scratch?

It seems I may be out of the woods. It's going to be a tedious solution, but at least I won't have to wipe anything or unroot or so on. Basically I have to uninstall and then reinstall everything to end the FC's and restore settings and data. It was actually the Maps update that helped me figure this out. I got the notification that there was an update so i followed it and upgraded. The fact that it notified me and then allowed me to download the new version told me the net was working. I also had another app that needed to be updated that was also fc'ing. So i upgraded that app and viola, no more fc and the 3g was working. So i uninstalled other apps that were giving me trouble with settings and data like Quick Settings and Tweetcaster, reinstalled and now I'm good money. I've got 144 apps installed so it's gonna take a few hours, but it's worth it to have my phone back. Thanks again for the advice.

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