Okay so this is my first post on XDA and I hope it's in the right section. Anyways I bought an HTC Incredible off a collegue of mine about two weeks ago. I got the phone and immediately rooted and installed a custom rom (MIUIv4 to be exact) I noticed after a lil while that the touch screen would randomly go berserk clicking things, calling people, etc (usually right after turning screen on) When the screen starts doing it I'd turn it off and back on and it would be completely fine. I thought to myself "maybe it's just a problem with MIUI and installed PONS CM7. I still had the same issue. Now whats strange about all of this is if I'm running an RUU or Stock based rom the screen NEVER acts up. I've read on several forums that this is a hardware issue but most people still experience it on stock roms, this is not the case with me. I won't deny that it could be a hardware issue, but it's an issue that can be solved with kerenl/dirvers/software. I'm wondering if I can use the drivers and software from a stock based rom to combat the issue and make custom roms run like they are supposed to. In all of my research I found this link which seems to be pretty promising but I don't know where to begin with it. Unfortuneately I can't post a link until I've posted 8 times, uuugh.
Edit: It seems the longer I run a custom rom the more frequently the issue happens.
If anybody is intrested in helping it would be greatly appreciated. I've been racking my head for over a week on this one. You can look up the blog I read on google. It looks like it could solve my problem.
Unresponsive touchscreen of Nexus S solved by tuning kernel
Related
When I first encountered the problem that my Hero device lower part touchscreen stop work "unresponsive" I tried a bunch of other roms, even stock from HTC.COM.
I have read a fair amount of threads with people that has the same problem. As far as I can tell there is no one at this time that know the solution or the root of the problem.
PLEAS everyone that have this problem post in this thread so that we are able to solve this irritating problem ones for all.
/Gekn
Things that I have tried
Flashed: Villian 10.2, Feeyo 1.7, 1.5.1, Modaco 2.1 r3, Stock hero unrooted, Modaco 3.2. Located the touch screens unresponsiveness with multi touch sensor apps.
GeknGekn said:
When I first encountered the problem that my Hero device lower part touchscreen stop work "unresponsive" I tried a bunch of other roms, even stock from HTC.COM.
I have read a fair amount of threads with people that has the same problem. As far as I can tell there is no one at this time that know the solution or the root of the problem.
PLEAS everyone that have this problem post in this thread so that we are able to solve this irritating problem ones for all.
/Gekn
Things that I have tried
Flashed: Villian 10.2, Feeyo 1.7, 1.5.1, Modaco 2.1 r3, Stock hero unrooted, Modaco 3.2. Located the touch screens unresponsiveness with multi touch sensor apps.
Click to expand...
Click to collapse
i also face the same issue. Intially i thought it was a ROM problem and flashed all the possible Rom's i can lay my Hands On but nothing seems to work. Its a hardware fault; digitzer or something it is called as.
Now my Hero just sits there without doing anything.
Its Hardware related. Had this too, tried also different ROMs with no help. Then i sent my device to Htc Support, they replaced the Touchscreen. After i got it back it was working for 3 weeks.
Now the same issue again. Have to send it back to htc.
-------------------------------------
Sent via the XDA Tapatalk App
If I remember right tou have to remove the fastboot or something "the thing that make the root paoosible" if your sending it to HTC.
Mine was send to HTC too for a new touchscreen.
No problems any more for 6 months now.
HTC told me its a very common problem.
Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
The data dropping out may be due to some work/upgrades in your area ... call VZW to see if they know anything.
As far as updating to GB, my advice is tread lightly ... especially if you're just wanting a stock version of it. There are bugs, the biggest being voice mail notifications not working, that may drive you nuts. That being said, there are several custom ROMs around that have fixes/tweaks that make this plagued GB build VZW & HTC released much more manageable. Look around and there are a few "stock" custom ROMs out there - or if you prefer a totally different look/feel there are several Sense 3.0 ports to choose from too.
As far as a how-to guide, the best one I've seen is THIS ONE. Read it and get knowledge my friend
Happy flashing!
2.11.605.3.zip is the [gb] patch - "It changes camera libs, and some insignificant
framework, and apks." as stated on teambamf.net, i did read it is running smooth,
increased battery life but,with issues pertaining to vm notification error and front facing camera
upside down. i agree with Yank talk with carrier, im currently running dasBAMF Forever
kernel 2.6.35.10 stock radios have had no issues.
vinny2006 said:
Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
Click to expand...
Click to collapse
Can you link me to that download? I would like to see exactly what you are making reference to before I comment.
Some of those update .zips are the full unrooted rom. You wouldn't want to flash that. You want to make sure and look for something like...
"Rooted Debloat Blah Blah Blah"
The link provided by Yank is a good one. #3 for "Flashing a Rom".
Also another hint (just in case you are unfamiliar with recovery). the camera buttons toggle up/down and the power button is used to make a selection. you can select "go back" by toggling to it and selecting it or you can use the soft back key.
hope that helps.
As to the voicemail issue, Eris has fixed that. Took him 30 minutes, he said.
Sent from my ADR6400L using Tapatalk
Did you read this?
http://teambamf.net/showthread.php/718-How-to-flash-a-ROM
Like the title states, my phone started rebooting multiple times today, I just flashed Eclipse2.0 the other day. I havnt had any issues at all until now. any help would be appreciated. If more info is needed let me know exactly what/ how to get that for you!! thanks in advanced!!!!
p.s. Ive searched forums for a solution, none seem to be relevant to what I am experiencing.
I get random reboots on all JB ROMs. I think its a fact of life until an official kernel is released. Please correct me if I'm wrong about the kernal.
Sent from Novena A3..... it's on fire!
I actually had it a while back too, I was on Black star. I was still under warrenty and had other issues, got a new one and no problem until now.
Hi everybody. I have been reading many of the posts here over the past 6 months and trying to learn as much as I can about different ROMs and issues related to my particular phone which is the Samsung Epic 4G Touch.
Thanks Exit_Only for your helpful work in this thread: http://forum.xda-developers.com/showthread.php?t=1975379. In that thread Sydius 08 asked "How are the Stable 1 tweaks running for you guys? Running CM10 11/18 nightly" I would like to focus on one aspect of that.
First I am currently running cm-10-20121117-UNOFFICIAL-d710 with gapps-jb-20121011-signed. I had installed JellyBeanMod_Stable-One_EO in hopes that it would resolve my long-standing GPS issue. I have read so many threads and I do appreciate all of the comments and attempted fixes by this community. I also use GPS Status and GPS Essentials where I see zero satellites but saw eight or nine instantly with #3 below. Here are the three times when my GPS has worked:
1) When I first got it just over a year ago. It was running Gingerbread 2.3.x (don't remember the last number but think it was 1). It worked perfectly but stopped after about 2 months and worked on and off after that.
2) After the GPS completely stopped working I started learning all I could about using a custom ROM. I tried CyanogenMod 9 but it did not resolve the issue. There's more to the story and more ROMs and tips provided here that I tried but all failed. However, whenever I Odin back to StockCWM-EL26.tar it works perfectly. I followed the tip about getting a fix prior to putting an ICS or JB ROM on.
3) I installed this on 11/15 http://sbrissen.chris41g.org/sbrissen-ALPHA6.zip and my GPS worked perfectly. However, lots of other apps failed miserably and it kept freezing up.
So here I am with nowhere else to turn. This latest CM 10 works perfectly EXCEPT the GPS. I would appreciate any thoughts on this.
i'm sure someone will mention this, but have you attempted to acquire a GPS lock on a stock ROM, for example, and revert to one of your desired ROMs?
smoresrock said:
i'm sure someone will mention this, but have you attempted to acquire a GPS lock on a stock ROM, for example, and revert to one of your desired ROMs?
Click to expand...
Click to collapse
Thanks for the reply and yes: "whenever I Odin back to StockCWM-EL26.tar it works perfectly."
[ROM]Phantom's Blazer Rom[Yo][8/2/12][v0.1.5][FF18] try this Rom seems to have GPS work in it
Shlickwilly said:
[ROM]Phantom's Blazer Rom[Yo][8/2/12][v0.1.5][FF18] try this Rom seems to have GPS work in it
Click to expand...
Click to collapse
Thank you. I had actually tried that one and ran into a problem with flashing it but I think that's because I didn't go back to StockCWM-EL26.tar first. I might give it a try again. I do love CM 10 and it would be perfect if the GPS worked.
For those who may not know this guy, QBKing77, is one of the best at teaching how to do this. Here is one for the SGIII and the Blazer ROM which he considers one of his favorites. I had to remove the link because I'm such a newbie. Here is the YouTube description: Blazer Rom on the Samsung Galaxy S III [REVIEW]
allenp007 said:
Thanks for the reply and yes: "whenever I Odin back to StockCWM-EL26.tar it works perfectly."
Click to expand...
Click to collapse
yep. this is the same method i used to fix my friend's GPS issue on a jelly bean ROM. after seeing to it that i was getting a GPS lock on the stock ROM, i went back into recovery, and flashed the ROM she wanted (paranoid android i think it was)... since then, she's been a happy camper locking into 7-9 satellites indoors
Great news! I was able to resolve this issue by following Qbking's YouTube tutorial: "How to Temporary Boot Stock EL29 on the Samsung Epic 4G Touch." I was able to lock on to 9 satellites and get a fix on my exact location. It was literally showing me in front of the building where I was standing.
I hope this helps someone else who might be going through the same problem with their GPS on an E4GT. If someone could post this information and possibly the link to the thread I referenced earlier I would appreciate it.
Thank you everyone for your comments.
I've been having this issue since I first flashed a LiquidSmooth ROM a couple months back, but as I've installed official CM10.1 and AOKP roms, the issue has persisted across them. Currently I have Avatar 2.13b on slot 1, AOSP r6 on slot 2 and LiquidSmooth 2.4 in slot 3 and the problem exists on all 3. Bluetooth will work fine on an initial flash, but a some point later on, it disables itself, and the only way to get it back is to wipe dalvik and reboot. Is this simply an instability of the kexec kernel, or something more. I've seen a few posts related to this, but not enough that it seems like a common issue. Any one else having this problem or any thoughts on why its happening to my RAZR MAXX xt912? Wiping dalvik isn't a huge inconvenience, as I typically only use BT to and from work, but after a long day in the office, not being able to connect my headphones can just add to my frustrations. Any thoughts or help is greatly appreciated, thanks in advance!
Did you ever make any progress on this problem? I'm having a similar, tho not identical, BT problem . . . posted it, hoping to get some idea how to approach it. Thanks
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
psudeke said:
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
Click to expand...
Click to collapse
Too bad. I was hoping to piggyback, or at least get some insight.
I like to think I'm not an idiot, but short of changing hardware I can't think of anything new to even try.