Database Develop

SLLOOWWW

Im not sure exactly how to word this so I will try my best; My tilt has been acting up lately. I touch a button and maybe a few or more seconds later it will finally load. Does anyone happen to know what might be causing it. (Sometimes it almost freezes) Ive tried to search but i dont know how i can paraphrase that.
Thanks in advance for any help!

lhsokkrfreak1327 said:
Im not sure exactly how to word this so I will try my best; My tilt has been acting up lately. I touch a button and maybe a few or more seconds later it will finally load. Does anyone happen to know what might be causing it. (Sometimes it almost freezes) Ive tried to search but i dont know how i can paraphrase that.
Thanks in advance for any help!
Click to expand...
Click to collapse
well to be able to answer your question i need to ask you one:
did you recently flash a wm6.1 rom to your device? if answer is yes, than you need to flash the newer hardspl onto your device by jockyw.
if not than the problem is most probably related to programs eating up your ram. Try disabling these programs from staying loaded at all times to save system memory or if you have alot of junk on your ppc than doing a little bit of house cleaning should help i.e. deleting temporary files, uninstalling unused cabs/programs, you get my drift.

lhsokkrfreak1327 said:
Im not sure exactly how to word this so I will try my best; My tilt has been acting up lately. I touch a button and maybe a few or more seconds later it will finally load. Does anyone happen to know what might be causing it. (Sometimes it almost freezes) Ive tried to search but i dont know how i can paraphrase that.
Thanks in advance for any help!
Click to expand...
Click to collapse
Did you ever try the first simple troubleshooting method: soft-reset?

pretty much.. start off slow before u get into the technical aspect.. if u can clear out ur cookies from ur browser, free up some space on ur memory, and soft reset..

sherpa said:
Did you ever try the first simple troubleshooting method: soft-reset?
Click to expand...
Click to collapse
You don't sound like you have much to lose, Back up personal data and " go for the gold " hard reset and start again. Then you will know for sure whether it is hardware or software.

Experiencing TouchFlo Delay from standby

I have done the Speed tweek with advanced configuration tool, and all was ok, I started experiencing crashes with the weather and programs menu, so I switched back to default, as the TouchFlo seems to work ok default anyway. Crashes seemed to have stopped but today I started to experience varied delays with the touch flo when coming out of stand by, I get the top bar with the windows logo straight away but the rest of the screen is just black, the delay is sometimes short (1sec ish) and sometimes long (5sec ish) doesn't sound much but when you want to use the device it is highly annoying, done multiple soft resets and pulled the battery out while on too.
Is anyone else experiencing this problem?
Rich

Anyone? any advice at all!!!!

richardirv said:
Anyone? any advice at all!!!!
Click to expand...
Click to collapse
advice: dont fiddle with something you dont understand, especially memory allocations.

jasjamming said:
advice: dont fiddle with something you dont understand, especially memory allocations.
Click to expand...
Click to collapse
I have only followed instructions from this site, I come here looking for help and everywhere I look your putting people down, how do you know what I know and don't know, I have used XDA's for years, I am not an expert but I can hold my own, but when I need help I thought this would be the place to find help not comments like that!!

I think these tweaks are setting the cash to a value higher than the memory available once you've opened a few programs.
I think whats happening is that because you set the cashe sizes so large the OS allocates the first 50% or so really quickly, then you run out of memory and you get the lag as it empties the cash.
When i get my phone i'll do some proper tests with hard resets inbetween. I would suggest you do a hard reset and start with much lower cache values, then slowly increase untill it breaks again.
The other problem with a huge cache size (fs) is that if the phone does crash you loose all that data in ram, potentially leading to corrupt files.

someone1234 said:
I think these tweaks are setting the cash to a value higher than the memory available once you've opened a few programs.
I think whats happening is that because you set the cashe sizes so large the OS allocates the first 50% or so really quickly, then you run out of memory and you get the lag as it empties the cash.
When i get my phone i'll do some proper tests with hard resets inbetween. I would suggest you do a hard reset and start with much lower cache values, then slowly increase untill it breaks again.
The other problem with a huge cache size (fs) is that if the phone does crash you loose all that data in ram, potentially leading to corrupt files.
Click to expand...
Click to collapse
Thanks for a constructive comment, does it matter that I had put the cache settings back to default and uninstalled the advanced config tool but still getting the same problem? Does it remember certain settings? Will probably try a hard reset when I get home tonight though.
Cheers

Seems to have fixed its self now!!!

Help G1 problem

Hi,
Recently I have been having a problem with my G1.
When I have left my phone on stanby for a period of time and I press the menu key to turn on the screen the screen back light comes up but it's blank.
I have to press the end key periodically to get the screen to come on this can take anything from 5secs to 1min. I have reflashed and wiped several times and tried different themes but it still does it.
I am running cyanogen 4.2.15.1 with the enoch theme updated via cyanogen updater.
It does not do this all the time it did it more with Darkstar.
I have been told I should re-root but I am worried about doing this because I am on the new radio and have been told I cannot flash back.
What to do???

Then why don't you just change roms and see if the problem still consists :S

Jonnibravo said:
...worried about doing this because I am on the new radio and have been told I cannot flash back.
What to do???
Click to expand...
Click to collapse
DREAIMG.nbh will over-write you radio and spl, no worries there if you wanted to go that way but I think it's a little too extreme. What you need to do is a complete wipe and stable rom with no a2sd or swap. Once that's running for you - start adding stuff 1 at the time. Sooner or later you will pinpoint the problem.
Good luck.

borodin1 said:
DREAIMG.nbh will over-write you radio and spl, no worries there if you wanted to go that way but I think it's a little too extreme. What you need to do is a complete wipe and stable rom with no a2sd or swap. Once that's running for you - start adding stuff 1 at the time. Sooner or later you will pinpoint the problem.
Good luck.
Click to expand...
Click to collapse
Ok I reformatted the partition and set it back up using amon ra 1.5.2 swap 96 ext 512 then installed super d 1.10.2 and slowly added apps to my a2sd, did on Friday no problem till Thursday afternoon it once again I pressed menu and the screen stayed black after pressing the end key repeatedly it came back up about 30 seconds later.
2 theories here
Could it be because I am using a class 2 sd card or
Could it be related to a lock screen, before I used lockbot though I uninstalled it it still happened noww I am using lock screen 2.0 the day after it started happening.

Cyanogenmod has always done this on every version I've flashed. Try a different release.

goldenarmZ said:
Cyanogenmod has always done this on every version I've flashed. Try a different release.
Click to expand...
Click to collapse
I am on super d 1.10.2 not cyanogen, do you mean a rom that does not use cyanogen guts???

hey i've also got this problem but it's kind of different, 1 im not running cyanogen, 2 it might be a hardware issue with your's as it is one with mine. So far i think its the flex cable but not too sure. My screen would go black and whenever i try pressing the home or something the device would just completely shut off. I would remove the battery and have to try and boot it up at least a couple of times before it decides to work properly.Any ideas? i might get a new flex cable but im not sure if thats the real problem.

Jonnibravo said:
I am on super d 1.10.2 not cyanogen, do you mean a rom that does not use cyanogen guts???
Click to expand...
Click to collapse
Super-D does use few CM bits and pieces in his rom but that's should not be the problem.
Do you use any home replacement apps?
Do you use a task manager?
If so, make sure that your taks manager is not killing your home. Do make sure that it kills other memory intensive apps when not in use
If you use stock home then make sure to check "Keep Home in memory" in the "Spare Parts", see if that helps.
Sounds like either a memory leak somewhere (one of the apps) or a hardware problem. Let's hope for the first.
And yes.... please get rid of that class 2 card ASAP. New class 6 8 Gb card is around $15 and will last your thru few devices so its a money well spent.
Good luck.

I pretty certain it's not a hardware problem as there is no pattern to when it happens, I do have a habit of installing different home apps as I like to try them all that could be the problem.
]I give that a try

Try cleaning the cache . Maybe there are too many things running in the background .

how bout you do a full wipe and try out super cdsi v4 rom its just about the fastest rom out there

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

Sleep of Death (SOD)- Shake to wake?

I can't post in the thread on SOD in the developers forum, so thought I would post my observations here.
I recently updated from CM7.03 stable (on SD card) to CM7.1RC (on SD card) on my wifes Nook.
Never had the SOD when running CM7.03 stable, but looks like I am now getting it.
Occasionally the screen wont come back on when pressing the power button. The nook appears to be on, but the screen is off. Ultimately, I have to hold the power button down until it shuts off and then restarts.
However, the last couple times this has happened, I have taken the nook and given it a heavy shake. Upon doing this, the screen turns on.
This suggests that maybe the SOD is related to the G-sensor operation?
Has anyone else tried to do this when experiencing a SOD?
Hope this helps.

Thanks for sharing. I should give it a try.

Next time I get this, I'll try it out too!

Nice, I will try this too. I have to admit occasionally I will get frustrated and shake it and occasionally it turns on but I thought it was me hitting a bunch of buttons and waking it. Volume, etc.
It's obviously still "on" since you have to do a hard power off on it. So, perhaps that's the magic?

Has anyone else had a chance to try it?
It still seems to be working for me (tried it 2x more times since I posted), but it could be a fluke.

This would be random to find out if it works. I'll try myself too next time I get a SOD.

I think it is more likely related to Wifi. Particularly, some app is not playing nice with the Wifi driver. Are you signed into Latitude in Google Maps?

It figures - now that I WANT my Nook Color to experience SOD, the damn thing is running fine!!!
I'm sure it'll happen again sooner or later (probably sooner) - I'll be sure to try the "shake to wake" idea and post my results!
Thanks for the info....

FYI - My SOD finally came and no matter how much I shook my Nook Color, it would not come back to life (boy, did I look like an idiot, though!)...
Oh well, it was worth a shot!

jtrosky said:
FYI - My SOD finally came and no matter how much I shook my Nook Color, it would not come back to life (boy, did I look like an idiot, though!)...
Oh well, it was worth a shot!
Click to expand...
Click to collapse
Darn no video of you trying that? OP should have asked for proof of people trying it. Haha
Sent from my PC36100 using Tapatalk

I just had an SOD and I shaked the Nook and nothing happened..

I just had an SOD and I shaked the Nook and nothing happened..
edit: Phiremod v7 Test.

OP is getting a good laugh thinking of all the people shaking their Nooks.

cincibluer6 said:
OP is getting a good laugh thinking of all the people shaking their Nooks.
Click to expand...
Click to collapse
LOL at all you shakers.
Oh well, it happened a few times on our Nook, haven't had an SOD since yesterday. Maybe it's a fluke or something related to our nook.
Oh well, I was hoping it would have been a solution.
At least I can get a laugh out of everybody shaking their nooks as if it were an etch-a-sketch.

Hmm, on the latest nightly, I noticed that I sometimes get a pseudo-SOD! The screen will not come on, but if I repeatedly push the volume up/down buttons, I can tell the Nook is still running (it beeps when you press the vol keys). I've found that when this happens, I just wait a few seconds to a minute and try turning it on again and it comes on (did NOT reboot either). I had this happen to me about 3 times within an hour today!
Now there is another SOD-related problem? Or maybe related to the original SOD problem? Try pressing the vol buttons the next time you think you have SOD and see if they beep. If so, give the nook a minute or two and try turning on again... just curious if anyone else is seeing the pseudo-SOD issue as well...
Thanks.

Just great. Now that I want it to have SOD so I can test this out, it's working awesomely. Maybe I should say i don't want SOD and it will sod.

In my best Steve Jobs voice: "You aren't shaking it right"