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
Related
hi
I have got a Nexus ,just after i got it i unlocked and root it after it changed the Rom .
now it hangs most time for example when i plug the charger sometime it hangs and a big X with an open lock appears and i have no way else to remove the battery.
and some time when i use the GPS and navigation it restarts.
i have tried many Roms and Radios but even when i want to go to recovery it hangs too ,and sometimes no.
i tried to switch to ERD79 (fastboot commands)but i found out that when i finish it,still the radio Ver. is 4.06.00.12_7 .
when i change the Rom or radio it restarts and restarts and some time hangs again.
so please help me to solve this problem
thanks
Did you wipe the data?
yeah ,
every time i wiped data .
what's your version of Hboot and recovery?
HBOOT-0.35.0017
recovery Build RA-nexus-V1.8.0.1
really need help ,i can not use the phone .
it sounds like a hardware problem, but could you try a new ROM see if the problem is still there?
well ,last night i tried cyanogen 6.1 with radio 5.12.00.08 but still have problems.
how can i become sure about the hardware problem ?
is there any test or something like this ??
few days ago one of my friends told me to try RUU.
actually i don't know what is RUU and where i can find it.
i have searched for it and found some for desire but not for nexus.
Since i've update my SGS to android froyo the Proximity sensor stoped working and the position sensor taken 30sec to turn the image...
I've used the test mode code to check hardware error, but there everything is working perfectly...
If I put the Android 2.1 the problem doesn't show up.
Does anyone have the same problem or solution?
Nobody has this issue?
Is quite strange... because if i put a Android 2.1 ROM everything works just fine, but with later version of android the sensors still working (using test mode from SGS Tools, I confirmed that the sensors are just fine), but the system takes a huge time (~30sec) to do something...
Please, if anyone knows anything that could solve this problem, please say something!
I think that in the first week that I had Froyo everything warked fine, but I'm not sure...
Is there any way to do a complete reset and set everything to default values including Hardware settings?
I've already done Factory reset and Full factory reset, by CWM and Code.
Nobody??? Anything???
Is this a genuine samsung rom you are using .
A flashed rom or a genuine Kies updated firmware .
jje
I'm now using a ROM official (sam***gfirmwares.co*) flashed by ODIN.
Should I try use Kies?
No i was just trying to rule out a flakey rom .
My usual suggestion is a wipe via ODIN
http://forum.xda-developers.com/showthread.php?t=882014
But i would stop at Eclair and see if its solved the problem if OK upgrade further .
jje
Its the same thing...
Its quite awkward, because only apendds in Froyo...
why not try a custom froyo rom, head over to doc's kitchen and cook yourself one up. also try lagfix, and any other speed up tweaks. how does the phone respond normally ?? without the sensors ? is it quite speedy or does it lag ??
The phone work just fine but when i turn the phone it take a lot of time to twist the image... I can even still interact with the screen until it turns...
The proximity sensor takes a lot of time too...
No one else has this problem?
touch screen on milestone stopped working right after downgrade from CM7 to 2.1 or even 2.2 and now when i try to go back to cm7 i get this weird bootloop
I've got a similar issue, but not permanently. I'm using stock froyo and for some reason touchscreen is not working or working improperly after turning on screen from lock. I need to wait a couple of seconds, turn on the screen once more and most of the time it's fine. Any advice?
both of you,
format your SD CARD/PARTIONS when you are downgrading.
some files from previous ROMS can be affecting the STOCK ROM functionality when it starts fresh after fresh install.
happened to me a couple a times,
just reinstalling (properly) solves this issue.
Hello guys
A few days ago I tried to update my I9000 from Gingerbread to ICS (this version if you want to know it exactly: http://forum.xda-developers.com/showthread.php?t=1363593 ^^)
Everything worked out fine till I got a bootloop through a (today) known bug. But now to my real problem: I tried to flash a stock-rom to my phone to solve the problem, but suddenly the process was interrupted by a blue screen!! It was a bit like going into the test menu through typing the code into the dialer, but it was during the flashing-process!
I haven´t found anything about this problem (I have only found a bug were the display is a bit bluish, but this is caused by the kernel. And I found something were the PC got a bluescreen, but I have found nothing about a blue screen on the phone.)
Fortunatelly the download mode was still working and I could flash another rom with ODIN, but does anybody know what kind of bug this is?
Thanks
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.