Database Develop

HD Unusable Slooooooow

Has anyone experienced the following:
I have tried several different ROMS. After I flash the ROM things go really well. All is working, running fast and then after 24 to 36 hours my device just gets so bogged down that it takes a long time to do anything. Any program I launch will easily take at least 30 seconds to launch if it launches at all. If i soft reset it does nothing for the problem. I have changed batteries to see if that helped (of course it didnt nor did I expect it too). All that fixes it is another hard reset.
Does this sound like an issue i need to send the phone into HTC for? Possible hardware issue? Could a bad SD Card cause something like that? HARD SPL? Anyone else been through this? thanks in advance guys/gals

mallman said:
Has anyone experienced the following:
I have tried several different ROMS. After I flash the ROM things go really well. All is working, running fast and then after 24 to 36 hours my device just gets so bogged down that it takes a long time to do anything. Any program I launch will easily take at least 30 seconds to launch if it launches at all. If i soft reset it does nothing for the problem. I have changed batteries to see if that helped (of course it didnt nor did I expect it too). All that fixes it is another hard reset.
Does this sound like an issue i need to send the phone into HTC for? Possible hardware issue? Could a bad SD Card cause something like that? HARD SPL? Anyone else been through this? thanks in advance guys/gals
Click to expand...
Click to collapse
Have you used cooked and shipped roms too?
If you have not tried, try to flash a shipped rom and see how goes. If it will go well then try to reflash with your preferred cooked one.
If you have already tried a shipped one, I don't know, it's a little strange. If you thik to have a bad SD card, try to use the pda without it. But I don't think it can cause all the things you have written.

I had a similler issue and a clear storage solved it.
after flashing your HD or any other pocket pc with cocked or original ROM, it always recommend it to do a cealr storage from settings-->systems--> clear storage.
do a clear storage and i am sure your issue will dissapear.
good luck

love is me said:
I had a similler issue and a clear storage solved it.
after flashing your HD or any other pocket pc with cocked or original ROM, it always recommend it to do a cealr storage from settings-->systems--> clear storage.
do a clear storage and i am sure your issue will dissapear.
good luck
Click to expand...
Click to collapse
well trying to backup the data on my card showed me it has major problems lol. thanks for the tip. will try to jsut format it and see what happens.

mallman said:
well trying to backup the data on my card showed me it has major problems lol. thanks for the tip. will try to jsut format it and see what happens.
Click to expand...
Click to collapse
What do you mean with "major problems"?
What you described is really weird.
I flash too all the time, but the HD never gets slow.
Is clear storage for your SD card then?

mcowly said:
What do you mean with "major problems"?
What you described is really weird.
I flash too all the time, but the HD never gets slow.
Is clear storage for your SD card then?
Click to expand...
Click to collapse
when i tried to copy stuff from my card onto my pc to back up the data it kep freezing up on my pc and became unreadable. i would have to take the card out and start again. Eventually i just formatted it and now it works great. No clear storage doesnt appear to be for the storage card but I tried it. I had so much stuff on my SD card that im sure my HD was trying to run programs and since my SD card was unreadable it was killing the device.

I had a similar problem, and I was forced to format my SD card too. Luckily I was able to save 95% of contents before to lose everything .I experienced some folders became unreadable (unaccessible), and card was full of "strange" folders with unreadable characthers and improbable sizes (I thought I had some terabyte ).
I think stock microsd isn't the best... Simply I must remember to backup it more often
Exactly like mallman, formatting solved the problem

dagosjt said:
I had a similar problem, and I was forced to format my SD card too. Luckily I was able to save 95% of contents before to lose everything .I experienced some folders became unreadable (unaccessible), and card was full of "strange" folders with unreadable characthers and improbable sizes (I thought I had some terabyte ).
I think stock microsd isn't the best... Simply I must remember to backup it more often
Exactly like mallman, formatting solved the problem
Click to expand...
Click to collapse
Well the only difference is that my problem came back this morning which was after formatting yesterday. I have determined my card is bad so I swapped it out for a new card and we will see how that goes. If my device is having the problem and i just take the card out my device runs like a champ, pop it back in and slooooow I agree, I will get my card on a regular backup schedule very soon. Well, once my ned 16gb gets here. This 8 gig is just too small lol

I ran into a problem like yours when using WAD 2 on my Polaris with particular cooked ROMS that seemed to have a SD card problem....see post on Lakeridge here where someone pointed out to me where the problem was coming from http://www.lakeridgesoftware.com/forum/showthread.php?t=14568&highlight=WAD+storage , the only way I fixed the problem was flashing to a different ROM.

namaste74 said:
I ran into a problem like yours when using WAD 2 on my Polaris with particular cooked ROMS that seemed to have a SD card problem....see post on Lakeridge here where someone pointed out to me where the problem was coming from http://www.lakeridgesoftware.com/forum/showthread.php?t=14568&highlight=WAD+storage , the only way I fixed the problem was flashing to a different ROM.
Click to expand...
Click to collapse
checking it out now. I can tel lyou that this has to be the porblem because of course my 8gb card wasnt the solution because my device is dog slow AGAIN lol
edit: ok i will try a new rom and see. I have had this problem with Dutty's and Dav, if it happens to a third rom I will try th estock ROM and if it happens there I am spellbounded

HD is not slow. If yours takes 30 seconds to respond, something is wrong. I would take a look at the SD card. I used to have this problem in my Athena, causing constant freezes and soft reset. When I did a sktools benchmarking, it was clear that the unit was reading and writing to the card extremely slowly. I reformatted the card with incorrect parameter causing that problem. After reformatting with the formating parameter, my Athena resume the nomal fast response.

mallman said:
checking it out now. I can tel lyou that this has to be the porblem because of course my 8gb card wasnt the solution because my device is dog slow AGAIN lol
edit: ok i will try a new rom and see. I have had this problem with Dutty's and Dav, if it happens to a third rom I will try th estock ROM and if it happens there I am spellbounded
Click to expand...
Click to collapse
Check out Johnpatcher's barebone ROM http://forum.xda-developers.com/showthread.php?t=472972. I find it runs excellent but you'll need to archive CABs of your favorite programs. The performance I think is great, commented about that in the thread too (WAD 2 on the ROM), I have like 70% - 65% free memory all day.

ok testing touch of HD with WAD2 to see if I can replicate teh problem. (fingers crossed)

mallman said:
ok testing touch of HD with WAD2 to see if I can replicate teh problem. (fingers crossed)
Click to expand...
Click to collapse
I had it running on Laurentis's ROM too without a problem. Shame he seems to have left. But i do really recomend the barebones ROM, at first boot it only used 10% mem.
Anyway, hope it works for you and keep those theme's coming

namaste74 said:
I had it running on Laurentis's ROM too without a problem. Shame he seems to have left. But i do really recomend the barebones ROM, at first boot it only used 10% mem.
Anyway, hope it works for you and keep those theme's coming
Click to expand...
Click to collapse
well i never had a problem with the shipped rom and WAD2. I can confirm that touch of HD rom also shows the same problem. I can try the barebones rom and see what happens then if it doesnt work i am going back to shipped rom because nothign beats WAD2 (in my humble opinion)
and ps. i have tried multiple SD cards so i confirmed that isnt the problem

mallman said:
well i never had a problem with the shipped rom and WAD2. I can confirm that touch of HD rom also shows the same problem. I can try the barebones rom and see what happens then if it doesnt work i am going back to shipped rom because nothign beats WAD2 (in my humble opinion)
and ps. i have tried multiple SD cards so i confirmed that isnt the problem
Click to expand...
Click to collapse
Maybe you might want to PM those cookers to let them know about the bug, it was prevalent on many Polaris ROMS too for some time. Good luck, the barebones ROM hasn't had any problems so far, its fast and very responsive but lacks the bells and whistles of the bigger ROMS.

Now that you are speaking of, I can confirm I was using WAD2 (the trial, I don't think is important...) when I had the problem.
I'm currently NOT using at the moment because too many problems still with TF3D and no more problem with microSD card.
At this point I think I'll wait a little before to try again
I too would like to use WAD!

just wanted to report back so far so good with the stock ROM. Ive rebooted and done all kinds of things that typically kill it with the cooked ROMs.

strange story!!
maybe you make too many themes??

mcowly said:
strange story!!
maybe you make too many themes??
Click to expand...
Click to collapse
lol, im guilty!!!
Well just for everyone's knowledge, still no problems with stock ROM so I am willing to say problem solved. I cant run a cooked ROM and expect to use WAD2 I will start PM'ing all the cooks I see tomorrow and letting them know this and maybe they know of a fix. Thanks for all the help everyone

Full wipe with out losing music[solved] i'm an idiot!

As someone who swaps roms out frequently but also keeps 14 gigs of music on his phone is there a place or additional partition i could set up to keep my music on so i can do full wipes before testing roms without having to spend 30 minutes backing up and then 30 minutes putting back my music

LesserAnimal said:
As someone who swaps roms out frequently but also keeps 14 gigs of music on his phone is there a place or additional partition i could set up to keep my music on so i can do full wipes before testing roms without having to spend 30 minutes backing up and then 30 minutes putting back my music
Click to expand...
Click to collapse
umm... do you format your sdcard every time you flash a new rom?

nope. I just know my music isn't found if i place it in a ext or a second fat32 partition and clearing only davlik before new roms still leaves me with fc's and more annoyingly an inability to use my contacts.

LesserAnimal said:
nope. I just know my music isn't found if i place it in a ext or a second fat32 partition and clearing only davlik before new roms still leaves me with fc's and more annoyingly an inability to use my contacts.
Click to expand...
Click to collapse
i don't understand what your problem is. what's your checklist when you flash a rom? wiping your phone doesn't touch your fat32 partition and wiping your ext just wipes your ext. so i'm not sure why you're hesitant to do a wipe.

Nobody knows what the hell your talking about. The only time you may ever need to reload all of your data onto your fat32 partition is if you repartition the entire card to modify your ext and swap partitions. Thats it. Otherwise the only other thing that you can do (as far as I know) is just back up your data to your computer. Problem solved.

Binary100100 said:
Nobody knows what the hell your talking about. The only time you may ever need to reload all of your data onto your fat32 partition is if you repartition the entire card to modify your ext and swap partitions. Thats it. Otherwise the only other thing that you can do (as far as I know) is just back up your data to your computer. Problem solved.
Click to expand...
Click to collapse
geez, i thought i was the only one who didn't understand what he was talking about. i thought i was having a MAJOR brain fart. good to know i haven't lost my touch.

grandomegabosses said:
geez, i thought i was the only one who didn't understand what he was talking about. i thought i was having a MAJOR brain fart. good to know i haven't lost my touch.
Click to expand...
Click to collapse
We haven't lost OUR touch, everyone else just doesn't listen to common-sense anymore...
OP, if your talking about using all of these as ringtones and posing them after a wipe put them in the media>audio>ringtones/notifications/alarms folders on your sdcard (If you must, then make them)

JAguirre1231 said:
We haven't lost OUR touch, everyone else just doesn't listen to common-sense anymore...
OP, if your talking about using all of these as ringtones and posing them after a wipe put them in the media>audio>ringtones/notifications/alarms folders on your sdcard (If you must, then make them)
Click to expand...
Click to collapse
i sure hope he isn't talking about ringtones because if he has 14 gigs of them he's got two problems:
1: why has he kept his secret of 14 gigs on his g1?
2: he has WAY too many ringtones.

grandomegabosses said:
i sure hope he isn't talking about ringtones because if he has 14 gigs of them he's got two problems:
1: why has he kept his secret of 14 gigs on his g1?
2: he has WAY too many ringtones.
Click to expand...
Click to collapse
Wow thats a LOT of contacts for one person, damn this sum undercover shi...You need to lower the amount of contacts you have OP.Or stop having so many songs what is that like 1K+ songs?

Sorry i'f im not being very clear. i'm sitting here with a flu and my thoughts aren't flowing very well.... lets see if i can pull it together briefly. I know wiping / factory reseting is not supposed to remove the files. In fact they are still there but i can only see them under debian not when i try and view them under windows. My phones media player also seems to be incapable of locating them unless i remove them entirely and replace them on the card again. I have all my music backed up on the computer its the process of selecting the 14 out of 90 gigs every time thats annoying. If i'm just causing more confusion ill try again when im not out of it.

and no they aren't all for ring tone purposes......... i just happen to listen to music every free second i can and don't like carrying around a separate mp3 player.

Ace42 said:
Wow thats a LOT of contacts for one person, damn this sum undercover shi...You need to lower the amount of contacts you have OP.Or stop having so many songs what is that like 1K+ songs?
Click to expand...
Click to collapse
8gig=~1750 songs.
14=~3252.5 songs

LesserAnimal said:
and no they aren't all for ring tone purposes......... i just happen to listen to music every free second i can and don't like carrying around a separate mp3 player.
Click to expand...
Click to collapse
Well highly recommend backing them up on your computer now. If you ever lose them...

2745 songs actually. And before anyone asks. it is all purchased. I have a very extensive CD/Vinyl collection.

LesserAnimal said:
. I have all my music backed up on the computer its the process of selecting the 14 out of 90 gigs every time thats annoying.
Click to expand...
Click to collapse
Its actually faster moving everything off the phone on to my computer and then back then re picking what music to put on my phone. I'm blaming it on this 16 class 2 card. I'm gonna test a wipe on this 4gig class 6 and hope it leaves everything working.

well the 4gig card worked and i feel very very very stupid.... i've been using this sd card from day one on this phone .i just assumed it was normal to lose everything. Sorry for wasting your time.

Its ok atleast you learned something new.

FINAL ADB SOLUTION: For those who couldn't get ADB with Recovery

1. Install HTC Sync 2.0.25 onto your PC (it came with your phone) (maybe the custom driver works but I haven't tried it yet)
2. Power off your device
3. Remove the battery
4. Plug in your USB cable
5. Insert your SDcard (any kind, it doesn't matter the type, i have 6 different cards and class associations in my possesion and have rooted all of my co-workers DI's today using all 6 cards for proof of concept, 9 phone total [Everyone wanted Wireless Tether)
6. Insert your battery
7. Hold Vol. Down button + Power button
8. Start and loop (you can start this before now if you wish, just has to be before entering recovery)
9. After the phone scans the sdcard choose "Recovery" and press the Power button.
*10. SOLUTION: As soon as the white screen appears just casually (don't be a speed demon) click IN & OUT your sdcard and continue to do so (keep clicking it) when the black screen with triangle appears. You will be listening for the last windows chime that identifies the USB has registered. But, you want to stop with your last sdcard click IN just before the last windows chime is sounded through your PC speakers. You might need to do this a couple times just to get familiar with the timing of the windows sounds on your computer system. Those phones that don't have to do this and was rooted first have a much earlier timing of when the Exploit is active.
11. Now go get Rooted using the steps on the first page of this post.

dymanese said:
1. Install HTC Sync 2.0.25 onto your PC (it came with your phone) (maybe the custom driver works but I haven't tried it yet)
2. Power off your device
3. Remove the battery
4. Plug in your USB cable
5. Insert your SDcard (any kind, it doesn't matter the type, i have 6 different cards and class associations in my possesion and have rooted all of my co-workers DI's today using all 6 cards for proof of concept, 9 phone total [Everyone wanted Wireless Tether)
6. Insert your battery
7. Hold Vol. Down button + Power button
8. After the phone boots up and scans the sdcard choose "Recovery" and press the Power button.
*9. SOLUTION: As soon as the white screen appears just casually (don't be a speed demon) click IN & OUT your sdcard and continue to do so (keep clicking it) when the black screen with triangle appears. You will be listening for the last windows chime that identifies the USB has registered. But, you want to stop with your last sdcard click IN just before the last windows chime is sounded through your PC speakers. You might need to do this a couple times just to get familiar with the timing of the windows sounds on your computer system. Those phones that don't have to do this and was rooted first have a much earlier timing of when the Exploit is active.
10. Now go get Rooted using the steps on the first page of this post.
Click to expand...
Click to collapse
is this while running loop.bat? it didn't say

vzw said:
is this while running loop.bat? it didn't say
Click to expand...
Click to collapse
yes run the loop.
I tried this for about an hour with no result btw.

Worked for me

Seriously , this is the EXACT same steps that has been posted numerous times before. When you speak of a Solution as something Final it SHOULD NOT involve trial and error steps that require timing or just *luck*.
What a waste of a post and thanks for im sure getting peoples hopes up.

Seriously , this is the EXACT same steps that has been posted numerous times before. When you speak of a Solution as something Final it should involve trial and error steps that require timing or just *luck*.
What a waste of a post and thanks for im sure getting peoples hopes up.
Click to expand...
Click to collapse
Yes you run the loop but not necessary to run in a loop. Yes it is about timing and similar posts have been made but I think I've written it with more detail.
These precise steps worked with the exact timing on 8 DIFFERENT phones yesterday. If its not working for you then perhaps you don't know how to follow directions well.
-------------------------------------
Sent via the XDA Tapatalk App

Ouch.... Burned by last post
dymanese said:
Yes you run the loop but not necessary to run in a loop. Yes it is about timing and similar posts have been made but I think I've written it with more detail.
These precise steps worked with the exact timing on 8 DIFFERENT phones yesterday. If its not working for you then perhaps you don't know how to follow directions well.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
You know, just because it worked for you doesn't mean it will for others....
I CAN follow directions well, and I can't get it reproduced. (though it may be because I'm already rooted?)

Just keep clicking that card in your own intervals after the white screen and you will get it. With my own proof I can contest that there is a BIG misconception that this is only achieved during the White screen. NOT TRUE!!!
Those steps are what I experimented with trying to root my own DI and it worked. I was not convinced I'd get it to work on other phones since It's been days and countless hours trying to get mine to connect to ADB in Recovery. So, one of my co-workers let me try it on his phone with his different card type, and one co-worker after the other, success! The root I did on MY phone was with an sdcard I bought that came with some of the phones (SanDisk 2gb). I didn't get a free card from VZW. I had FASTER success with this card of all 6 cards I've rooted with. It took longer with the other cards, class 4 PNY, and off-brand class 6 cards. With the 2gb SandDisk class 2 it works on the first try for every phone I've tried.
Did you have HTC Sync installed as your active driver, I really can't say if the customer driver works as I haven't tried it myself? My laptop is the latest Sony VAIO F-series with Core i7 with Windows Ultimate x64. In Device Manager, while in HBOOT my phone only showed up as Android 1.0 and as HTC Bootloader.

dreamersipaq said:
You know, just because it worked for you doesn't mean it will for others....
I CAN follow directions well, and I can't get it reproduced. (though it may be because I'm already rooted?)
Click to expand...
Click to collapse
No, and if you want to be in tune with the FINAL SOLUTION, your chakras must be aligned with Lady DI and her mysterious ways. I recommend balancing her on your head while you sleep for a fortnight, and then comes the sacrificial goat!
Seriously OP, I followed the last CARD CLICK prophet's advice and now my card mushes into lock--the DI just ain't built for the kind of abuse frenzied insert/ejection creates. I respect that you're good at what you do, but as others have found, teaching timing with http very difficult, at best.

I installed root by using an old laptop with XP... I had one point installed the HTC drivers. In this case, I had unistalled the HTC drivers and the HTC sync driver. Now I only used the SDK usb.inf drivers with the modified line for HTC incredible.

rynosaur said:
No, and if you want to be in tune with the FINAL SOLUTION, your chakras must be aligned with Lady DI and her mysterious ways. I recommend balancing her on your head while you sleep for a fortnight, and then comes the sacrificial goat!
Seriously OP, I followed the last CARD CLICK prophet's advice and now my card mushes into lock--the DI just ain't built for the kind of abuse frenzied insert/ejection creates. I respect that you're good at what you do, but as others have found, teaching timing with http very difficult, at best.
Click to expand...
Click to collapse
Oh CHAKRAS! Formula 51 reference FTW!!!! B.E.S.T. M.O.V.I.E E.V.A.R.R.R.R.!.!.!.!

dreamersipaq said:
Oh CHAKRAS! Formula 51 reference FTW!!!! B.E.S.T. M.O.V.I.E E.V.A.R.R.R.R.!.!.!.!
Click to expand...
Click to collapse
Believe it or not, I haven't seen it yet--just added it to my Netflix queue tho.
OP, can you get us a dmesg of you hitting the timing with your method? I want to see how it reacts to mounting/checking the sdcard devices more than once in recovery boot. I think good dmesg logs would help us all figure out what's going on here . . . .

From what I've seen
rynosaur said:
Believe it or not, I haven't seen it yet--just added it to my Netflix queue tho.
OP, can you get us a dmesg of you hitting the timing with your method? I want to see how it reacts to mounting/checking the sdcard devices more than once in recovery boot. I think good dmesg logs would help us all figure out what's going on here . . . .
Click to expand...
Click to collapse
It depends on how quick you insert/remove. It takes anywhere form a 1/2 second to 1 second between the initial "Slot changed from 0 -> 1" to where the card is actually mounted. If you click too fast, you never that that "mount" so you'll never get root, since it seems like the "mount" is actually causing the error we need. If you slow down your insert/remove to a slower pace, you'll get numerous mounts of the sd card. This might increase your chances of getting root because you're mounting multple times, but it makes the mounts more random then precise timing, and unfortunately, to get our error that we need, the read needs to happen at a percise time. You've seen the dmesg that was posted by 'mite.

THANK YOU OP! Worked for me :-D
My other 2 incredibles had worked consistently, but this one took your process to get.

dreamersipaq said:
You've seen the dmesg that was posted by 'mite.
Click to expand...
Click to collapse
Yeah, and I'm still wondering why he was so 'elliptical' about explaining what was going on there. I still can't figure out if it's the mount process or the mounted card that triggers the adbd event, or if a delayed sdcard process simply pushes adbd start into the recovery window, when commands such as 'adb shell' can be received by daemon for a split/few seconds. Would be nice to hear his explanation of what system events are occurring outside of what is logged in dmesg. The OP says mount event can complete in recovery/black screen, you say sdcard mount must complete before black screen, that's a big diff.
I wonder if it's possible to create a host-side script that reads dmesg, watches for card mount and triggers 'adb shell' at a much faster rate than a simple win shell 'loop'. That would be killer, and would eliminate all need for card insertion timing, IMO.

rynosaur said:
Yeah, and I'm still wondering why he was so 'elliptical' about explaining what was going on there. I still can't figure out if it's the mount process or the mounted card that triggers the adbd event, or if a delayed sdcard process simply pushes adbd start into the recovery window, when commands such as 'adb shell' can be received by daemon for a split/few seconds. Would be nice to hear his explanation of what system events are occurring outside of what is logged in dmesg. The OP says mount event can complete in recovery/black screen, you say sdcard mount must complete before black screen, that's a big diff.
I wonder if it's possible to create a host-side script that reads dmesg, watches for card mount and triggers 'adb shell' at a much faster rate than a simple win shell 'loop'. That would be killer, and would eliminate all need for card insertion timing, IMO.
Click to expand...
Click to collapse
I don't think so. Don't have the devices in front of me right now, but I believe that the phone is disconnected from the PC (that first do - do) before our window of opportunity, which means the pc is not communicating with the phone at all. So if (big if) I am correct, nothing local to the PC can be done to initiate anything AT THE TIME that we need it to.

dreamersipaq said:
I don't think so. Don't have the devices in front of me right now, but I believe that the phone is disconnected from the PC (that first do - do) before our window of opportunity, which means the pc is not communicating with the phone at all. So if (big if) I am correct, nothing local to the PC can be done to initiate anything AT THE TIME that we need it to.
Click to expand...
Click to collapse
Dat's kinda what I thought

I'll try to get you guys a dmesg as soon as possible. I'm at work right now and I'm responsible for alot of servers at a law firm in DC. (never get any free time it seems) I'm been trying to check in with you guys as often as I can. It's brutal today because we have Maintenance tonight throughout the morning.

This is what I found by myself to work for me after trying for 3 days originally.

Say what you will about the OP, but the timing is key and his post did help me out. I've tried tons of cards, every method out there and had no luck, until now. So for what's it's worth, this post was much appreciated.

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

Why does my SD card keep disappearing ?

So I have to reboot my Galaxy S about 10-20 times a day -- every day -- because it disappears all the time. I have an external card in there too - but that too goes missing.
Anyone know how to fix this ?

no one knows why this happens ?

no one has EVER had their SD card disappear randomly and have to reboot ?
I don't buy that.

Apparently the 51 viewers as of this post haven't had this problem.
I certainly haven't.
Maybe someone that has, will show up.
​

It's just super annoying

Funkadelick said:
It's just super annoying
Click to expand...
Click to collapse
Might help to know what firmware and apps you are running.​

maybe you need to format the card inside the phone using the built in format app. Maybe you have a fake card. Maybe you have bad phone, in that case get it looked at

happened to me for a few days too.
Went uninstalling everything (tried a bunch of podcast/rss readers trying to find something that could handle passworded podcast feeds) as well as the games I was trying out and a few apps.
Hasn't happened since so one of them had to be the culprit.
- Completely vanilla sgs-i9000m from Bell, just unlocked. Not even rooted.