The soft keys were lighting up just fine, I have installed BeastMod II vs 2.1 and am using Go Launcher everything seemed to be working the first day and now the second day, the soft keys do not light up anymore. Does anybody know why this has happened or a possible fix?
Edited: Idk their exact name, soft keys, on screen buttons. (If theres any confusion...)
did you install any new Kernel for BLN ?
@Allgamer, no i did not install any Kernals. Only the Rom mention and Go Launcher
Edited: Installed Jaug's Rom it started working now, could have been a rom bug...
So this started happening back when I was using CM 7.1 before the new year, one day I wanted to use my camera and it would not load, just gave me a blank screen with no camera controls or anything nor would any apps that required the camera would work either. The only button I could push was the home button to go back to the home screen, if I waited long enough the camera would force close or say something about connecting to the camera. I flashed to a few other aosp roms, don't remember which ones, but the same thing happened, except when I tried the 4.0 evolvr rom, so fed up with having no camera I went back to multiple sense roms where my camera worked on all of them without any issue. Now I'm on the Evo Classic rom and my camera again isn't working, my guess would be due to it being a sense/aosp hybrid.
I had looked up solutions to this problem and the only thing I had found was to hard reset the phone by pulling the batter out for a minute and then putting it back in. I tried this but instead of having to have the batter out for a minute I needed to have the battery out for about an hour, too long or too short and the camera still wouldn't work. I've tried fix permissions, wiping camera data, redownloading and reflashing but nothing has worked.
My current setup is Classic Evo 0.0.6 preview with anthrax test 009 kernel.
My question to you guys is there anything I can do about this or will i just have to stick with pure sense roms in order to have a working camera?
Thanks again for all your help.
I'm no professional, but if you are having issues with using AOSP ROM's, and NOT Sense ROM's, then the logical choice would be to use only Sense ROM's since there seems to be an issue between those types of ROM's and your hardware. It may not be ideal since you obviously seem to prefer the AOSP ROM's, but unfortunately in order to get the functionality you desire you may have to suck it up and go back to Sense. I would suggest the Express ROM by Outerdepth...I'm using it right now and it BAMF! Still in Beta, but most bugs are worked out and everything works, like 4G. It's got good battery life and its really fast. Just a thought.
Try a full wipe of your phone, like data wipe, cache, dalvik, system, etc. Flash a stock ROM then data wipe/factory reset and flash whatever ROM you desire. I've had the same problem and that worked.
Thanks Supreme, it worked, I think I figured out what the problem was too, I kept using a superwipe before flashing roms but this time I didn't and it works.
Frostbiter said:
Thanks Supreme, it worked, I think I figured out what the problem was too, I kept using a superwipe before flashing roms but this time I didn't and it works.
Click to expand...
Click to collapse
No problem man, glad it worked.
I just upgraded my old Evo 4G to this phone about 3 weeks ago. On my Evo I was running CM7 and loved it. I tried installing a version of CM7 from a different website and after 5 minutes of running without any issues, my menu button started to glitch out and press itself. I couldn't use any of the other buttons while this was happening. I eventually shut the phone off and restored back to stock. After that I came back to this website and tried flashing Cyanogenmod 9 Alpha 6 and MIUI. Those both had the same issue. I have no issues using stock EL29. Is it just my phone or is this a common E4GT issue? Is there anything I can do to get around this? Thanks in advance.
It's a common problem on some ET4G phones. I'm on my third(bricked 2) and mine does it on every ROM I've tried, even stock. My first two phones didn't do this, but this one was driving me nuts. It was almost unusable. I had to run AOKP that has the option to remove use of the hardware buttons and just use the on screen nav buttons. Since doing that, I've had no more annoying constant menu pop ups. The downside is that I can't use any of the cool TW roms that are available, but at least I can use my phone. You could take it to your local Sprint store and get them to give you a replacement if you can duplicate it while you're there. I decided to keep mine because I've already gotten two replacements and I'm just tired of dealing with it.
Rats! That's not the answer I was hoping to read. I was hoping it was just a kernel issue and not an actual problem with the phone itself
I have d this problem still waiting for a replacement
Sent from my SPH-D710 using Tapatalk 2
Well it's good to know that this issue isn't my fault! I will take it to a Sprint store and see what they can do for me.
PLEASE SEE BOTTOM OF OP FOR UPDATES
-----
Greetings all,
[Backstory]
I've been flashing ROMs for about a year now. I started off with Virtuous Team Gingerbread and the Sense 3.x ROMS. I had no issues.
Then I moved to CM7, and MIUI, also on Gingerbread. No problems.
I've been using the CM9/CM10 ROMs since they appeared for the Incredible 2, from AOKP and Aeroevan, respectively.
Here is where the problems start.
[Problem]
On ICS and JB ROMs, I get what I have dubbed (there is probably a better name for it) "Phantom Touch Input".
At first I thought this was caused by normal bugs and glitches in the ROM. I did my best to deal with it. Usually a simple lock/unlock would solve the issue, temporarily.
So what would happen? Without touching the screen, I would get the long press menu to show up, and then the screen and capacitive buttons would freeze. Or the screen would start to slowly half scroll to the side, and again, freeze.
The most annoying part is when I am typing on the phone. I have tried other keyboards, be it from the MIUIv4, or the default keyboards of 4.0.x, 4.1, or 4.2. All the sudden random keys are pressed, and continue to be pressed, even when my fingers are nowhere near the screen.
However, no one else seems to have this issue, so it looks like I am the lone wolf here with this problem.
Can anyone provide insight? A possible fix? Or am I forced to deal with this on all 4.x ROMs?
---
UPDATE 1: Issues also occurred on CM7.2, so I may be facing a hardware issue.
UPDATE 2: Issues occurred in 4ext Touch. Looking around on YouTube, others (Incredible S users) have similar issues.
Nearly confirmed as a hardware issue.
Check Page 2 for video links.
[::AP::] said:
Greetings all,
[Backstory]
I've been flashing ROMs for about a year now. I started off with Virtuous Team Gingerbread and the Sense 3.x ROMS. I had no issues.
Then I moved to CM7, and MIUI, also on Gingerbread. No problems.
I've been using the CM9/CM10 ROMs since they appeared for the Incredible 2, from AOKP and Aeroevan, respectively.
Here is where the problems start.
[Problem]
On ICS and JB ROMs, I get what I have dubbed (there is probably a better name for it) "Phantom Touch Input".
At first I thought this was caused by normal bugs and glitches in the ROM. I did my best to deal with it. Usually a simple lock/unlock would solve the issue, temporarily.
So what would happen? Without touching the screen, I would get the long press menu to show up, and then the screen and capacitive buttons would freeze. Or the screen would start to slowly half scroll to the side, and again, freeze.
The most annoying part is when I am typing on the phone. I have tried other keyboards, be it from the MIUIv4, or the default keyboards of 4.0.x, 4.1, or 4.2. All the sudden random keys are pressed, and continue to be pressed, even when my fingers are nowhere near the screen.
However, no one else seems to have this issue, so it looks like I am the lone wolf here with this problem.
Can anyone provide insight? A possible fix? Or am I forced to deal with this on all 4.x ROMs?
Click to expand...
Click to collapse
Not exactly sure, I would say its hardware if it happens on all the roms. Have you went back to CM7 or MIUI since this problem started? I would revert back to one of them and test for a couple of days to see if the problem continues. If the problem is only active in ICS or JB then someone else will have to give you a hand on a resolution.
ThePhantom97 said:
Not exactly sure, I would say its hardware if it happens on all the roms. Have you went back to CM7 or MIUI since this problem started? I would revert back to one of them and test for a couple of days to see if the problem continues. If the problem is only active in ICS or JB then someone else will have to give you a hand on a resolution.
Click to expand...
Click to collapse
Ok will do when I have the chance.
Thanks for the speedy reply.
But let's say it is a hardware issue...
Do I unroot/restore/whatever and bring it back to Verizon?
Thanks.
[::AP::] said:
Ok will do when I have the chance.
Thanks for the speedy reply.
But let's say it is a hardware issue...
Do I unroot/restore/whatever and bring it back to Verizon?
Thanks.
Click to expand...
Click to collapse
Yes if the phone is still under warranty
I'm so fresh you can suck my nits...
Flashed CM 7.2
My home button didn't work, but that doesn't really matter.
I still experienced the same issues.
On a side note, wow CM7.2/Gingerbread is smooth....damn kernel. But stock 2.3.x is so ugly
Anyways, it seems like I should just "start clean".
I'm not sure what that entails - not just a full wipe...something more...tips?
[::AP::] said:
Flashed CM 7.2
My home button didn't work, but that doesn't really matter.
I still experienced the same issues.
On a side note, wow CM7.2/Gingerbread is smooth....damn kernel. But stock 2.3.x is so ugly
Anyways, it seems like I should just "start clean".
I'm not sure what that entails - not just a full wipe...something more...tips?
Click to expand...
Click to collapse
I use 4ext recovery myself, and I do a "full wipe" by format all partitions/factory data reset, then I see a lot of people also say wipe cache and dalvik so I throw that in as well, it don't take long but just in case a factory reset don't get them I just do it...lol. Hope that helps, and that may clear up some bugs with ICS and JB roms if you weren't doing that before. Just make sure you do a backup before wiping everything. Wouldn't want you to be without a phone if some process hiccups.
Thanks for the info.
Should I do anything with my SD card? It shouldn't affect ROM performance, but a wipe wouldn't be a bad idea, yes?
[::AP::] said:
Thanks for the info.
Should I do anything with my SD card? It shouldn't affect ROM performance, but a wipe wouldn't be a bad idea, yes?
Click to expand...
Click to collapse
I doubt that the SD card would affect the performance, but as long as you have backups of everything you can do as you please, backup backup backup. You don't want to lose everything, trust me I have seen bad things happen to guys that don't backup, and I have learned from experience as well.
Right right I know.
I'll try 4ext on a fresh ROM and see how things go.
Not a good idea to flash the touch version of 4ext in light of my issues.
Did a Nandroid, hit back, then screen input froze. The on-screen time is updating, but are the capacitive buttons are lit up but do not respond/give haptic feedback, let alone the touch screen itself. Power button just moves to the power menu, where I again cannot select anything.
Pulling battery :/
This is why I will never (want to) purchase a phone without a removable battery.
So looks like my issue isn't software related. (This issue can in no way be software related [or even caused by], right?)
I've had the phone for over a year...but I guess I'll try with Verizon.
*sigh*
What a pain.
Looks like I am certainly not alone.
(Better video) http://www.youtube.com/watch?v=25CaiveQoQg
(Similar) http://www.youtube.com/watch?v=kANVkc-Sk74&feature=related
I'm just really pissed off. And there isn't a phone in the market that I want.
That looks like possibly a bad digitizer, you can replace that fairly cheaply if you are out of warranty. That would be my best guess, and keep in mind I am no expert. Here is a link so you can see the process:
http://www.youtube.com/watch?v=LQL9gakQyuI
ThePhantom97 said:
That looks like possibly a bad digitizer, you can replace that fairly cheaply if you are out of warranty. That would be my best guess, and keep in mind I am no expert. Here is a link so you can see the process:
http://www.youtube.com/watch?v=LQL9gakQyuI
Click to expand...
Click to collapse
That is what I was thinking.
I'll also see if I can milk anything out of Verizon. I'm already an unhappy customer, given the lack of ICS, especially when promised.
Yep, digitizer.
http://forum.xda-developers.com/showthread.php?t=1399085
Good luck with Big Red, and let us know if you get it resolved.
ThePhantom97 said:
Good luck with Big Red, and let us know if you get it resolved.
Click to expand...
Click to collapse
Thanks, I'll keep everyone updated.
I'm sure I'm not the only one who has had issues. Hopefully word spreads, especially to those still under warranty who are suffering from a faulty digitizer.
Hi folks,
I'm not sure what's up with my phone. I have CM10 beta on it and since earlier today the D button on the keyboard is completely unusable. Also, I have a hard touch hitting R. I have tried touching the same area in other apps and it seems to work fine. Maybe there's a tool out there I could use to confirm this?
I had this happen before on an earlier build of CM10. When it happened before (and as of now), rebooting doesn't fix it. Last time I gave up and just upgraded my CM10 ROM, and it has been working ever since (around a month or so).
Today, the touch screen experienced some "glitches". What I mean is, I took it out to use it and it seemed like it was detecting touch/drag events in various spots, and I had to put it to sleep to get it working again.
I have no idea where to start with diagnosing this. It doesn't seem to be a hardware issue, since re-flashing before fixed it. Any ideas?
Go back to stock, if you have the same problem then it will probably be hardware issues.
Sent from my One V using xda premium