My touchscreen has become really glitchy, Swipes aren't smooth and it registers unwanted taps. I'm not sure if this is a software/kernel issue or maybe just the system getting bogged down for some reason. I started having this problem after installing tiKtaK 4.4 GPE ROM so I switched over to Viper 3.5 but I'm still having the same issue. Anyone else had this problem? I'm tempted to try flashing back to stock to see if it fixes things but I'd rather not if I don't have to.
UPDATE: Flashed to Viper 3.1.0 which was the last ROM I had loaded before the touchscreen issues started. Still having problems. I'm beginning to wonder if it's a hardware problem but I can't see why since the phone hasn't sustained any physical damage... Gonna try flashing to a stock + root ROM to see if that helps any :-/
gallasm said:
My touchscreen has become really glitchy, Swipes aren't smooth and it registers unwanted taps. I'm not sure if this is a software/kernel issue or maybe just the system getting bogged down for some reason. I started having this problem after installing tiKtaK 4.4 GPE ROM so I switched over to Viper 3.5 but I'm still having the same issue. Anyone else had this problem? I'm tempted to try flashing back to stock to see if it fixes things but I'd rather not if I don't have to.
UPDATE: Flashed to Viper 3.1.0 which was the last ROM I had loaded before the touchscreen issues started. Still having problems. I'm beginning to wonder if it's a hardware problem but I can't see why since the phone hasn't sustained any physical damage... Gonna try flashing to a stock + root ROM to see if that helps any :-/
Click to expand...
Click to collapse
Sounds like a hardware issue to me if you have changed software 3 times and it's still happening.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Related
Anyone else having issues with LED notifications(there are none) with the new atrix port version 0.4?
The rom seems to be really fast and issue free otherwise.
I haven't had any led issues. So far it works fine. I did only install it yesterday though. I was actually on the verge of throwing this phone through verizons window till I got this rom installed.
The one minor bug is that the default keyboard seems to hang up once in a while. I have turned off the Vibrate on Keypress and I think that will help. I will post back if I have any led issues.
hmmm...weird...thanks alot for the reply...ill try reflashing...
oh and one more thing...did you flash overmind's speedy scripts? wondering if thats what caused it...
i had the same led issue when i was on the .4 port... i went back did a wipe (3 times) reinstalled after re-downloading and it went away. but after it went away i started having serious lag issues. .3 was alot better than .4 in my opinion
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Chakker3D said:
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Click to expand...
Click to collapse
You are using a leak or *beta* rom which is far from stable
And no installing many roms can not damage any hardware
Sent from my GT-I9100 using xda premium
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Chakker3D said:
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Click to expand...
Click to collapse
Having a similar, if not identical issue on latest Westcrip ROM. Near as I can tell, seems to be related to memory management: while on BT, RAM space drops almost 200Mb. While changing songs, or surfing the tracklist/phonebook, it can cause the RAM to reach a critical level. This causes the OS to crash and the phone to reboot (my case a soft reboot from the animation only) in order to create space. I would chalk this up to inefficient memory management by a beta ICS rom. Look for this to be sorted out in the future with official releases and custom kernels/roms.
Thanks for your response.
Yeah when I installed resurrection, I also ran in to that problem. I had no idea how to diagnose it. But it makes sense, bottling up the ram to the brink of reboot.
Thats what initially was happening to me, soft boot, took a few seconds and was back in. But extended crashes seemed to cause corruption.
Yeah so the XXLPH seems to have an issue. Because I also tried foxhound and got the same result.
I just got back in from testing my BT on my car stereo using my stock rom of KG2 and it played for 20 minutes and i chatted for 19 without any problems.
So I am glad it wasnt anything seriosu. But only reason I was concerned is I found nobody else to have the problem and I felt a bit isolated
But im reading the official ICS rom is out in Europe so im sure we will see some new roms out in the next little while.
Recently my touch screen has not been working so well. The bottom 1/4"-1/2" works sporadically and sometimes it goes crazy acting like I'm touching different parts on the screen rapidly when I'm not touching the screen at all. I don't know if this is a hardware or a software issue. Anyone have an idea?
Specs:
CM10
Baseband 1.12.1.1119
Kernel : 3.0.51-geb1844c
Did you update the touch screen? It is in Captain Throwback's thread with radios and stuff. I'm not sure if CM10 supports it, but you need to be on a rom that is based off the newest build. Otherwise the update will make your touch screen inoperable and have to go into bootloader/adb to flash a supported rom.
I have noticed that my capacitive buttons are less consistent on the Sense 5 rom. Maybe it is just me, I'm not sure.
Anthonicia said:
Did you update the touch screen? It is in Captain Throwback's thread with radios and stuff. I'm not sure if CM10 supports it, but you need to be on a rom that is based off the newest build. Otherwise the update will make your touch screen inoperable and have to go into bootloader/adb to flash a supported rom.
I have noticed that my capacitive buttons are less consistent on the Sense 5 rom. Maybe it is just me, I'm not sure.
Click to expand...
Click to collapse
I did the 3.15.651.16 update, but not the 3.16.651.3 because all my software was a little older.
Anthonicia said:
Did you update the touch screen? It is in Captain Throwback's thread with radios and stuff. I'm not sure if CM10 supports it, but you need to be on a rom that is based off the newest build. Otherwise the update will make your touch screen inoperable and have to go into bootloader/adb to flash a supported rom.
I have noticed that my capacitive buttons are less consistent on the Sense 5 rom. Maybe it is just me, I'm not sure.
Click to expand...
Click to collapse
I am having the EXACT same problems as described in OP. I have updated the touch screen via Captain Throwback's thread. I am currently running 3.16.651.3 with Mean Bean. I have tried Stock with Goodies also but the problem persists. Over the weekend I unrooted the phone just to see and I noticed that the touch screen was back to normal. I am running out of thoughts on this one. Sprint has offered to replace my phone but I hate to do that if there is nothing wrong with it until I root again.
The touch screen issue started before I did the firmware update. Everything I did was right when root, unlocked bootload and s-off became available a year ago. Then the issues started and I updated the firmware to 3.15, which didn't change anything.
phoenix0783 said:
The touch screen issue started before I did the firmware update. Everything I did was right when root, unlocked bootload and s-off became available a year ago. Then the issues started and I updated the firmware to 3.15, which didn't change anything.
Click to expand...
Click to collapse
My issues started recently, I have been upgraded for some time now. I am starting to wonder if it is a rogue app update or something else along those lines.
If you are having sporadic issues with the touchscreen not working, particularly if it doesn't work if you touch it in a certain spot, the issue isn't with your touch panel driver. The issue is most likely the touchscreen itself
Sent from my EVO using xda premium
My dad (who uses an iPhone) and a few other people have been complaining that whenever they call me, they get really bad static or sometimes even echoed feedback during phone conversations. I've tried multiple different ROMs and he says it still happens sometimes. What confuses me is that its kind of random when it happens because other times it'll work perfectly. The mic isn't broken or damaged because recording apps don't have this problem. Is it something in my settings and/or the ROM causing this? Any feedback is appreciated.
I'm currently using the latest shoshock ROM and have in the past been using tasks AOKP, which is where it first randomly started.
Are you using the ajk kernel? If you use the wrong one, you'll get that affect. FYI shostock should have mic swap kernel.
Phalanx7621 said:
Are you using the ajk kernel? If you use the wrong one, you'll get that affect. FYI shostock should have mic swap kernel.
Click to expand...
Click to collapse
I used the default one that was in the flash able zip. Unlike most ROMs, it was an all in one package so nothing else was required.
First, you want to know if this is an intermittent hardware issue. The troubleshooting test for that is flash back to stock and observe. If the problem is still present, then it is very likely to be a hardware issue.
If not, then the problem is most likely in firmware somewhere. Since this is not a common problem, and since you have had it on multiple roms, it would probably not be due to the kernel or system firmware, so you would have to look at applications to see what might be interfering.
Hello friends,
I recently picked up an i717 and am in the process of sorting it out. It was originally a Bell phone, though of course it's unlocked these days. I've been hacking at various Android phones for years now and have managed to work through just about everything, but this has me stumped...
I've tried almost all the 4.4 roms, and most of the 4.3 as well. I've tried various kernels/modems/combinations/etc. I've used CWM and TWRP. They all invariably lead to the phone either rebooting constantly from the "optimizing apps" dialogue, or a few times I've made it to the welcome screen, but it's always just up for a minute or two, crashes, then reboots. I haven't found a live download for 4.2 yet, so I don't know if it would work or not. 4.1 stock and Padawan run just great. I've been doing multiple full wipes before installation, flashing the rom a few times, then hitting the caches a few more times for good measure. I can't imagine my flashing technique being at issue here.
I do know that there is at least some physical damage to the phone. The capacitive buttons don't work. But it doesn't see immediately obvious to me that these would be related. Of course, I've seen stranger things. Running Padawan the phone will hum right along at max speed all day with no apparent issues, so that side of the hardware seems okay.
Sometimes CM roms will end up at the CM welcome screen and pop up a "com.android.acore has stopped" dialogue. But the constant reboots are there on every rom I've tried.
Does anybody have any ideas?
Outside of the, every once in a while you just need to go all the way back to stock just to make sure all the garbage is taken out, have you considered the infamous stuck power button?
Though I have yet to, many have experience the stuck power button. It may feel ok and you may even hear it click, but that doesnt mean anything. Give your phone a couple good flicks to the back behind the button. Though it does seem odd that it would run one rom without issue and not others, but it is worth a shot.
Again taking your phone to 100% stock every blue moon or so can be a good remedy too.
Keep us posted. We can work you through this.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I thought about the power button issue. However, it proceeds to boot into the OS until after a time when the screen locks then reboot, which would seem too long to be the power button in any case. Regardless, a few sharp flicks didn't help much. And, of course, it runs quite happily all day long running on 4.1.
I have restored to stock JB, though admittedly not earlier than that. I guess I could try going all the way back to GB to see if that makes any difference.
In my experimentation tonight I've found that 4.2 also does not work, while I can add 4.1 non-tw roms to the working list. My best guess seems like something about one of the many under-the-hood things that changed with 4.2 doesn't get along with something about my particular phone. But, who knows.
For now I'll try rolling back to GB in Odin and see where that gets me.
I would say ICS is about as far back as you need. Recently I was having issue getting anything 4.3 and up to work or even flash. No different recoveries had effect either.
Wiped slate clean and started over from ICS, and Bob was my uncle. Everything that failed before was not an issue. Running latest 4.4 now and might I say "Orgasmic"
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ahh, if only I were on 4.4 on my Note, life would be good Though, to be honest, I'm quite digging this thing, even at 4.1.
Last night I rolled back to GB, and had no luck. Although the Odin tar that I found apparently didn't include recovery, so that had to be flashed separately. I don't know if that might make a difference. That might be my experiment for tonight if I can find a tar that includes everything. Might be easier to find on ICS.
Just running my mind through other stuff I've thought of, I remember reading about kitkat having some issues with SD cards, so I've mostly been experimenting with the card pulled and a fresh format on the internal storage, with no real difference. Tried safe mode, no dice (not that I would expect this to make a difference on a fresh flash, but who knows lol...).
It's just such a weird thing. It boots into the OS with seemingly no issues. On occasions when I can actually get to the lock screen, everything runs fluid as can be until it freezes and reboots. Sometimes when it gets stuck at the 'optimizing' screen it'll just restart the count every boot, sometimes the number of apps to be done go down each time until there are 3-4 left which persist through each reboot.
I wonder if I could check logcat via adb before it reboots. Might be able to find some clues there.
Here's a factory firmware image of 4.1.2 to be flashed with Odin.
http://www.mediafire.com/view/g7gn29h7nu63id5
I've used this to revert many times. Install it. Run it once, then factory reset and run it for at least a few hours. If you experience issues you probably have hardware failure. If you don't have issues you can proceed with installing the latest clockwork mod recovery. Then wipe system and internal memory 3 times with recovery. Now flash the zip of your favorite kit Kat rom. Reboot and run it. Then factory reset and hopefully run it forever! If you're on a kit Kat build and experience sd card issues, there's an xposed module that might be able to help with that.
Thanks a lot, Bro. I'm downloading the image right now and will flash it then give it some time to settle in. Fingers will be crossed!
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Bassism said:
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Click to expand...
Click to collapse
Have you tried to turn on USB Debugging and run "adb logcat" to see what errors are causing the problem? If it is an optional program or hardware feature you may be able to disable it and run the newer ROMs. I know bluetooth has been an ongoing pain point for people. Which modem are you running? I know that some of the older modems do not work with the newer ROMS.
Good luck.
Brett
corrupt radio
i had the same issue, flashed 4.4.4 and ran like a charm for 1 day them the radio took a dump. downgraded and worked for another day.
imei became unknown and the no radios were able to fix this. went as far back as 2.3.6 hoping my radios would be fixed and no dice.i have tried endless for weeks to fix my phone and seems doomed.
none of the bricked threads helped and flashing stock with odin is no help. there seems to be no fix to the null imei and unknown baseband