So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Cheshire-Cat said:
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Click to expand...
Click to collapse
try in stock rom/eclair about a week ,I think it is about nAa issue !!
just full wipe and flash stock rom..........using flash tools......or try using song update service........
binhari said:
just full wipe and flash stock rom..........using flash tools......or try using song update service........
Click to expand...
Click to collapse
I did, as I stated before. Still not working properly.
What I don't understand is how flashing a new kernel/ROM can break it in a way that not even flashing back stock Eclair solves the problem. I can only think of hardware failure but... it would be akin to a computer failing because you installed a different version of Windows.
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
illusionist.h1 said:
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
Click to expand...
Click to collapse
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Cheshire-Cat said:
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Click to expand...
Click to collapse
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
illusionist.h1 said:
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
Click to expand...
Click to collapse
I don't know exactly how ROM flashing works -- I've seen a "backing up system files" message, and I think that there's a reason why the stock 2.1 image is about 200 MB while CM7 ROMs rarely exceed 100 MB. I guess that some files are kept. Maybe if one or more of those files (say, a driver) is replaced with an incompatible version... but then, flashing stock should solve it. Maybe someone can shed a bit more light on the subject?
Another possibility is software-caused hardware failure, where some kind of misconfiguration physically damages the hardware. It's very uncommon, but who knows.
Related
Hey guys I just flashed Darky's Rom v8.1 on my Samsung Captivate and i really like it but I have two problems. The first one is an auto rotation opposite rotation problem. The screen auto rotates the 90 degrees the wrong way so if i hold it vertically, the screen is horizontal. I calibrated the horizontal axis but it didnt work. The only solution I have found is to turn off auto rotation but then i cant use the qwerty keyboard when emailing or texting. My second problem is that when i download apps it restarts into the Darky's rom screen and reboots back to the home screen with the app no where to be found. Is there anyway you guys can solve one or both of my problems, or even suggest a better rom because im up it P.S. please keep in mind this is my first android phone and Im more or less a noob with this phone (not technology but just the phone)
Sounds like a bad flash.
You can, reflash the rom
Our try a different one
What kernel are you using?
I have not used darkeys but this is not a common issue with the rom
Darkyy
Dupontrocks11 said:
Hey guys I just flashed Darky's Rom v8.1 on my Samsung Captivate and i really like it but I have two problems. The first one is an auto rotation opposite rotation problem. The screen auto rotates the 90 degrees the wrong way so if i hold it vertically, the screen is horizontal. I calibrated the horizontal axis but it didnt work. The only solution I have found is to turn off auto rotation but then i cant use the qwerty keyboard when emailing or texting. My second problem is that when i download apps it restarts into the Darky's rom screen and reboots back to the home screen with the app no where to be found. Is there anyway you guys can solve one or both of my problems, or even suggest a better rom because im up it P.S. please keep in mind this is my first android phone and Im more or less a noob with this phone (not technology but just the phone)
Click to expand...
Click to collapse
The problem you have with autorotation is because you loaded Darkyys ROM from the I9000 forums. To resolve this issue, use a captivate Kernel. Use the K12O kernel from http://forum.xda-developers.com/showthread.php?t=893880
Flash it in CWM Recovery.
Hopefully your second problem gets resolved after resolving the first issue. I have Darkyys 8 and using it with the SpeedMod kernel, without any issue..
@rickysa2000 your kernal worked amazing and my phone is mega fast and the auto rotation is back to normal but I still can't download an app successfully. Since i downloaded the kernal, half the time the download is successful and installs and half the time it goes back to the Darky's screen but for both, the app still isn't on my menu. Maybe I'm just being dumb and it's right under my nose, but either way I still cant find it!
Try this
Go to settings
Applications
Manage
market
Clear data
I tried it and it didnt work. I also tried to download other apps besides quadrant standard and that sent it into the darky's screen as well. Any other suggestions? Is there a place where I can see my downloads besides the pull down menu (which doesn't show it) to see if it got downloaded to some obscure place?
Just an idea, but why not download gaskets from the captivate section, and flash it again. I have never encountered your issue but if I did I would either reflash, or flash stock then reflash
Try flashing ytt3r's Captivate port, as he mentioned fixing several bugs present in the I9000 version:
http://forum.xda-developers.com/showpost.php?p=10133066&postcount=1
(it's the big "DOWNLOAD HERE" link)
Thanks everyone! I'm downloading the newest Darky rom from ytt3r but for the mean time I just flashed phoenix which works great. But as I was flashing it, I noticed a nice scratch. AHHHH
Dupontrocks11 said:
Thanks everyone! I'm downloading the newest Darky rom from ytt3r but for the mean time I just flashed phoenix which works great. But as I was flashing it, I noticed a nice scratch. AHHHH
Click to expand...
Click to collapse
haha.. cats don't like captivates
mcord11758 said:
Just an idea, but why not download gaskets from the captivate section, and flash it again. I have never encountered your issue but if I did I would either reflash, or flash stock then reflash
Click to expand...
Click to collapse
lol10charararar
I have had the same problems with auto rotation on some Darkys roms and others, I reflalshed the roms , it seemed to fix the problem. I am running Darlys 8.1 fash, good battery life and now bugs with no-wipe flash.
when I touch the screen or use swype the touch is not recognised properly and it jumps around quite a bit.
Dont know why its happening but im on 2.3.3 rom and I did install the with bootloader version.
Been working fine since this morning but its getting more and more tempremental and I havent made any changes either.
Anyone know what could be wrong?
you'd better flash to any froyo rom,if the issue is still happen,your phone may have a hardware problem
Factory reset first .
jje
I am considering upgrading to 2.3.4 on my galaxy mini to solve the "sleep of death" problem... is anyone out there who has upgraded to 2.3.4 still having the "sleep of death" problem?
Whats sleep of death problem ?
It's when the phone is still "on" but will not wake up. The only way to get it working is to take out the battery. Many are reporting this happening every day or two.
Happens on i9000 for me, I just keep powerbutton pressed until it reboots. No need to remove battery.
I think i need to do a factory reset on phone + sd card someday, maybe it resolves it.
this happened to me too. just reset phone and when it starts, try to use the phone or just simply tap the phone every time it tries to sleep (anything works as long it doesn't sleep)... just keep on doing this for about 30min? or more
(make yourself busy while doing this cuz its gonna be boring just tapping)
I think it's related to hardware problem (not confirmed yet anyway)... Don't believe that "upgrade" could be the solution..
I actually hope so!
GT-S5570 on Train
I just upgraded today using kies.... now when I try to start up it never gets past the step where it shows the "Samsung Galaxy Mini" text. Creating another thread for this problem.
With CheckFUSDownloader (thanks to Luffarjoh - search 3D) you can download the archive used to update your fw and, so, reflash it with Odin (even more times if needed)...
GT-S5570 on the road
Doc_cheilvenerdi.org said:
I think it's related to hardware problem (not confirmed yet anyway)... Don't believe that "upgrade" could be the solution..
I actually hope so!
GT-S5570 on Train
Click to expand...
Click to collapse
Nope, it's not hardware related. Never had a SOD since I used tjstyle's CM7.
Early Gingerbread firmware from Samsung has SOD too, but I think the latest versions doesn't.
Official firmware is now on 2.3.5, FYI.
If I can't get passed the logo screen what is the best way to get my firmware information? The guides say I need this info to choose the right rom.
Thanks!
This is a Froyo problem, didn't happen in Gingerbread :3
Yeah, had the same problem when on Froyo, after flashing GB2.3.4 the problem hasn't occured.
Hi .. am facing weird problems with my mobile.. It started of yesterday suddenly when i tried to unlock the device . I was using kang's RC1-80 + Etana's 28 march LOC kernel (default values- no undervolting or overclock)
1. doesn't wake after locked (major problem)
2. frequent hang ups
3. accelerometer not working
4. media playing too fast and no sound
I have tried different Roms - Kang's build of cyanogen(GB), Nova-HD, MIUI GB (with and without etana's kernel).
I have also tried raising the minimum frequency to 503mhz but of no avail.
Can you suggest some solution and help trace the problem.
You think maybe it's hardware?
Why not trying to return the phone to full stock with smartflash? If it's still acting weird can you still return it on warranty?
Thanks for the reply.. I tried flashing with smartflash to stock rom but still the same problem persists. I will be taking it to service centre then..
Best of luck to you mate.
Maybe if it starts suddenly it can be something unusually, sdcard, sim card, or try other kernels. Maybe problem with recovery (but stock rom should help).
Sent from Poland
It happens randomly when using the phone (it doesn't happen when it's locked). The phone just freezes then restarts randomly.
I tried to find a pattern when this is happening, and found there isn't much of a pattern, but it won't let me add a fingerprint lock (crashes after the 3rd / 4th reading).
I've tried to factory reset and clear cache. I'm running out of options and am preparing to flash a stock ROM via Odin. I'd like to avoid this, since it'll trip knox and this is a new phone so I wanted to avoid flashing anything for now.
Any suggestions, ideas?
I'd say this is a kernel related crash, since it doesn't give any error, just goes out. But I hope I'm wrong.
Baseband: N920CXXU2BPD5
Build Number: MMB29K.N920CXXU2BPD6
Knox untripped.
EDIT: This seems to be a rule: it always crashes when I get to 32% of adding a fingerprint lock.
Here's an update:
Tried flashing other stock ROMs for other regions, still the same problem.
Flashed a custom kernel, still the same problem. -> Not a kernel problem
Flashed TWRP and used it for some time (to test if the phone will do the same). No problem whatsoever. I'm convinced that this is a firmware issue then.
Tried flashing every possible combination of everything. Nothing seems to have any effect. This isn't a software problem.
It's probably a faulty motherboard. The rebooting subsided though.
I'd also like to add that the S Pen holding area (the place where the S Pen is kept inside the phone) has a specific electronic smell (kindda like the soldering smell, but not quite). Really weird.
I voided my warranty by flashing stuff, so I'll probably be looking at a motherboard replacement if anyone's wondering.
Do u have xposed install?
Nah.
I've been running the stock rom for 90% of the time.
RexGrammer said:
Nah.
I've been running the stock rom for 90% of the time.
Click to expand...
Click to collapse
U solved it already? Mine used to have this problem before but its xposed that cause (in my case :highfive
Still haven't.
I'm almost certain it's a faulty motherboard.