Related
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
mine is unresponsive sometimes and i have to tap on the back of the phone to get to work again. i thinks its going out soon
That's what I thought about my old one, I figured I had dropped it to much.. because I did lol but now I got a new one 2 weeks old and I'm running into the SAME problems.. I'm assuming I must be doing something wrong with how I've got **** set-up
j18yo said:
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
Click to expand...
Click to collapse
j18yo i think that your problem might be that to many programs run when you start your vogue that happened to me before and i hated it but then i heard of a program named "Space Reclaimer" FREE and it made my vogue much more responsive because the program stops any programs that start when you turn on your vogue or any windows mobile phone
I have the same problem usually under the same conditions. Mostly happens in the morning after the device has been off. Works fine for a few seconds then stops responding correctly i.e., the D-Pad stops scrolling correctly with a lag on touch response. I use CleanRAM and it still doesn't fix the prob once it occurs. Sometimes when I run CleanRAM it will occur. I've tried putting biotouch.exe and everyting BUT the kernel processes in the exceptions list and a Level 1 clean. Hard reset yesterday and haven't had the problem yet. If it continues to work, I'll post my settings.
BTW, I'm on a stock 6.1 ROM with a few apps.
j18yo said:
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
Click to expand...
Click to collapse
What ROM are you running? I asume that wehn your new device came you loaded it the same as the old one. It has to be something with the ROM you are runnning or a problem with a program causing your issue.
My phone would do this periodically too, with Vin's latest ROMs. I turned off Manila and am running Titanium now. Interestingly - no lags when unlocking since. I'll keep Titanium on for some time to see if that makes it go away. I had an issue with both his current v2 and v4 (which I am running now).
Ive had to replace my screen twice and the whole phone once because of touch screen problems. Thank God for the insurance.
Ah yes... to what OP mentioned:
I do not beleive it is a more pressure thing. I do not think it is more pressure that is required but rather that the phone is non responsive. If you are unlocking and typing a PIN, it takes the PIN and all but it takes perhaps one digit every 5 seconds. That's my experience anyway. So it is just slower, as if something was consuming the CPU and UI is not responsive.
crazylegs91 said:
I have the same problem usually under the same conditions. Mostly happens in the morning after the device has been off. Works fine for a few seconds then stops responding correctly i.e., the D-Pad stops scrolling correctly with a lag on touch response. I use CleanRAM and it still doesn't fix the prob once it occurs. Sometimes when I run CleanRAM it will occur. I've tried putting biotouch.exe and everyting BUT the kernel processes in the exceptions list and a Level 1 clean. Hard reset yesterday and haven't had the problem yet. If it continues to work, I'll post my settings.
BTW, I'm on a stock 6.1 ROM with a few apps.
Click to expand...
Click to collapse
THIS..
It has to be the problem.. I have CleanRAM run every 12 hours or 6 hours because I figured it would help.. lol but now your saying sometimes it happens WHEN you run cleanRAM.. Im assuming it does something, or erases something it shouldnt?
This is like the 1 sole thing I have run on a schedule, I've turned off my email and everything to manual, I went into my startup folder and there was about 4-5 things I didn't need which made the battery 100% better than it was in terms of how long it lasts.. and I set-up this CleanRAM schedule on my last phone I THINK I forgot but I do know as soon as I got this 1 going I did it and I'm bout to delete the program completely and see if it'll help, I have speedbooster too which does a cleanup too I'm curious if it would have the same result..
I'll let everyone know if this ended up being my problem incase anyones in the exact same boat with the same apps
PS: I was doing level 3 cleans
j18yo said:
THIS..
It has to be the problem.. I have CleanRAM run every 12 hours or 6 hours because I figured it would help.. lol but now your saying sometimes it happens WHEN you run cleanRAM.. Im assuming it does something, or erases something it shouldnt?
This is like the 1 sole thing I have run on a schedule, I've turned off my email and everything to manual, I went into my startup folder and there was about 4-5 things I didn't need which made the battery 100% better than it was in terms of how long it lasts.. and I set-up this CleanRAM schedule on my last phone I THINK I forgot but I do know as soon as I got this 1 going I did it and I'm bout to delete the program completely and see if it'll help, I have speedbooster too which does a cleanup too I'm curious if it would have the same result..
I'll let everyone know if this ended up being my problem incase anyones in the exact same boat with the same apps
PS: I was doing level 3 cleans
Click to expand...
Click to collapse
Update: I don't think CR erases things as much as it kills processes that won't restart. Thru trial and error, I've adjusted my CleanRAM settings to where I haven't had the problem for a couple of days. I'm able to do a Level 3 cleans on a once a night schedule and during the day if need be. In settings, I have it to close all apps, launch startup progs, and display today screen. I have no exceptions listed for either running progs or startup progs. I have the most up to date version from the OTA update in the program.
The program links in my StartUp folder are: poutlook (original on ROM), sddaemon (original on ROM), WLMUpdate (original on ROM), Glossybars.exe (I added this), biotouch.exe (I added as I thought CR killing this was the source of the problem), pocketwit.exe (I added), and SIPChange (I added).
One thing I did do was delete the link for TouchPal from the Startup folder. I did this for other reasons (I use FingerKeyBoard). Not sure if this was part of the problem.
I can scroll with d-pad and no touch lag.
On a side note, can I delete any of poutlook, sddaemon, or WLMUpdate from the startup folder to save battery power?
I'm probably just a bit above a newb so sorry if I don't make sense.
Update: Just for kicks, I deleted the links for glossybars.exe and pocketwit.exe from my StartUp and it started locking again after running CleanRAM. I put them back in and it works again even after running CleanRAM. Maybe someone with more knowledge can explain this. I'm just keeping it the way it is now...
Hmm weird that you removed something not very important like pocketwit an cleanram caused problems again.. someone has to have some info on this??
I deleted everything from my StartUp folder but my SPB Mobile Shell.. I didn't have sddaemon, but I did have poutlook and WLMUpdate both of which I deleted.. then I had some other programs that aren't necessary for the phone.. I have no problems on restart or anything, and the % showed being used is stays around the 30's now instead of 40s/50s.. and when I run programs it usually reachs 50% tops now instead of 60/70% I used to get.
PS: Pocketwit isnt bad I used to praise the program but now I've tried MoTweets and.. I can't think of the other one now.. ****.. it's really good though but it seems to use a lot more phone power than MoTweets so I went back to that.
Pocketwit kept giving me problems, started saying I need to install that NET 3.5 or whatever but when I try to it says I have a later version already so it won't install, then other times it'll work completely fine.. but MoTweets I like better anyways
Ok, I give up. I restored everything to the way I had it when it was working and now I'm having problems again. After the screen turns off and I turn it back on, it locks up and won't scroll and has the touch lag issue.
Hope someone figures this out. Shouldn't have messed with success. Good luck.
crazylegs91 said:
Ok, I give up. I restored everything to the way I had it when it was working and now I'm having problems again. After the screen turns off and I turn it back on, it locks up and won't scroll and has the touch lag issue.
Hope someone figures this out. Shouldn't have messed with success. Good luck.
Click to expand...
Click to collapse
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
bigboy292000 said:
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
Click to expand...
Click to collapse
I'm running a stock Sprint 6.1 ROM. Thanks though.
bigboy292000 said:
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
Click to expand...
Click to collapse
I'm not using the TouchFLO interface, does that mean its still on though?
I'm not completely up on understanding all this
This was happening with Vin's Rom for me as well. I was tripping out pressing ON so many times with no screen showing up but phone light on! I believe it could be the power settings. I disabled the "Turn off device" which I believe was mentioned in his notes about the rom.
I gave up on this problem for a while but found something when researching how to disable to cube. I used the registry edit in this thread to disable to cube post #69. I didn't do any of the other steps because I'm not having memory probs (42% with pocketwit in the bckgrd).
http://forum.xda-developers.com/showthread.php?t=368269&page=7
I noticed that biotouch.exe never shows up in the running processes menu in CleanRAM and I don't have the "lock/freeze" scrolling problem any longer and I can run CleanRam without the problem occurring. I can press any item on the screen as well with no delayed response.
However, this stops you from being able to finger scroll and do the "side to side" scroll in Messaging. I never really finger scrolled and prefer using the d-pad for scrolling so losing that functionality isn't a big deal to me.
If anyone can figure out how to keep this working so smooth and have the option to finger scroll, I'd be much obliged. It just seems that biotouch.exe craps out sometimes and locks up the d-pad. If they could both work equally well....
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App
Hey guys, my txt and mms stuff constantly freezes and gets stuck, I already applied the patch from HTC that was supposed to fix it and it made it worse it seems like, does anyone else have this issue? It doesn't seem to matter if I have alot of conversations saved or if Ive deleted them all, it still randomly crashes and gets stuck and it eventually clears but its getting to the point where I really hate this phone. When I first got it it was great this never happened, and I haven installed any apps or anything and its getting progressively worse, not sure what the issue is but I almost cant even txt anymore without a 50/50 chance of it crashing and stalling.
seriously no one else has this problem? I look at task manager and: Messaging (TXT & MMS) is always stuck.
I think all of us have that problem. I am being serious. The reason why I say that is because no matter the ROM (stock, custom, my own) I still have wonky issues with MMS, SMS and freezing, or Blank Screen of Death.
Sorry to not have a solution for you...
ah, I thought maybe I was the only one or something, hmm, that sucks, almost makes me want to just run android all the time, it just seems to suck the battery away and some stuff doesnt work great, unless Im not using the best android setup.
I wonder if its part of TouchFlo3D, Im gonna turn on windows default stuff and see what happens that way, Ill try that for a day and see if I Constantly crash/get stuck and have ot wait for minutes randomly on every sms
Ive had the same problem! Ive resorted to Valkryie's ROMs, they have lots of features and are REALLY fast! I love energy ROMs,and i use them like 60% of the time, but when Im going out for a while or like when im going on Vacation, im gonna use Valkryie, but anyway, havent had a problem yet with the sms freezing.
I'm a first time poster. I have searched the Q&A section a few number of pages about my problem and I can't find anything.
My phone likes to press a certain area of the touch screen without me touching it at all. I don't really know what else to call it except "ghost inputing". Sometimes when I go to input text or when I'm at the home screen, it decides to go crazy. If I'm typing up a text message, if in portrait, my phone likes to type Q's even when I definitely don't want to. If I'm in landscape, a bunch of spaces and period is what it likes to press. If I'm at the home screen, the phone likes to pick up an app or open it.
It gets pretty annoying, especially when I'm just trying to reply to someones message. My only temporary way of fixing it was to turn on and off the screen. Sometimes it takes awhile.
I have tried flashing a stock 1.47 ota rom but it didn't really help, actually made it worse. Touch screen responsiveness dropped significantly, so i flashed back down to like 1.32 (responsiveness came back).
I got my phone the day it was released, so I don't even know if I can bring it back to Best Buy or not. Any kind of suggestion would be great... this problem can really bring my spirits down sometimes, especially when I'm showing off my phone to random people when they ask me. Kinda embarrassing to have my phone freak out when it's supposed to be a high end device....
Sounds like a warranty thing. I'd hit up htc.
Sent from my EVO from the Apple Store.
Im having the same problem making my phone useless :/
I have been trying to bring this issue to light for sometime!!
I have a topic on it already if you guys want to add to it but the end result for me right now is trying to get the phone exchanged..
http://forum.xda-developers.com/showthread.php?t=741242
I have had the same problem.
Turning the screen on and off sometimes makes it go away. It seems like it started when I rooted (simple 3 click). Not positive about that though.
I'm now running Fresh 3.1.0.1 and it is better.
-Steve
svennn said:
I have had the same problem.
Turning the screen on and off sometimes makes it go away. It seems like it started when I rooted (simple 3 click). Not positive about that though.
I'm now running Fresh 3.1.0.1 and it is better.
-Steve
Click to expand...
Click to collapse
Try running some of the older ROM's not based off the .47 OTA or the newer froyo and its gone completely for me..
Ive sort of tried to search this one (How do I search JUST the Epic 4g section of XDA??) and found no one describing this problem the way I do...
This is my second time having this issue, and the fix for it last time was a pain in the ass, so id like a new fix-
Every app, every aspect of my phone, continuously resets/reloads. This is most noticeable with Hancent SMS, as it saves a message as a draft when you close out of the app... Well, right now, ill be typing and "message saved as draft" will constantly pop up at the bottom of the screen (about once every 2 seconds), and the phone will lag and it will erase 1 or two characters(making me look like I cant type :silly: ).
If this was the only problem, maybe I could live with it, but it affects everything. Launcher Pro randomly/continuously resets. The notification bar often resets while trying to pull it down. The phone app will close or freeze as soon as I start receiving a call. Sometimes it'll play my ringtone without a way for me to answer, other times I never knew I missed a call unless they leave a voice mail... And sometimes its worse than others, sometimes its fine for an hour, then something goes stupid and even a reboot doesn't help. For instance, right now, it was happy. I launched aLogcat to check it out and now the screen orientation REFUSES to stay one way. Even setting the phone down, it switches directions every few seconds, which makes aLogcat reload and therefor its unusable.
I haven't mentioned what im running because Ive had this exact same issue on a totally different rom, almost a year ago, but im running-
build - SleeperROM_3.0.0_FC09
kernal - 2.6.35.7-Shadow-FC09_v1.0
baseband - S700.0.5s.FC09
firmware - 2.3.6
Ive had this happen on EB13 on the EpicExperience ROM too.
SOO, if anyone has advice on how to fix this, id be extremely interested.
On the other hand, last time I had this issue I was convinced it was a corrupt piece of memory somewhere early in the OS, something I corrupt during install, and I went ahead and reflashed and wiped and reflashed and wiped and returned to stock and etc. etc. etc... and that seemed to work... actually, I dont know exactly what part of the process fixed it, thats why I do not want to repeat it unless I have to... BUT, if someone would like to explain/point me in the right direction. I'd like to know how to DELETE AS MUCH AS POSSIBLE and FLASH as CLEAN as possible. (that is, if no one else knows of a fix for my problem)
thanks all!
Err, well only thing I can think of is a truly clean install using Odin. This means do not restore any data from backups. Then slowly begin installing applications 1-by-1 through the play store website (for speed sake) to see if your issue creeps up again.
It also couldn't hurt to format your SD card too. Corrupt data on the SD card can cause some wonky things at times.
get another device...i hope u have the equipment protection plan
Thanks for the advice guys OFF TO THE ODIN MACHINE! haha.