I upgraded my C6J6 to the latest Mirek v7 ROM and it had been working fine except the camera until yesterday, the touchscreen completely stopped working. Mine does not come with Windows, I only use Android. I flashed the BIOS to 2.02 and reinstalled ROM again, but still the same issue.
Is this a hardware or software issue? Anyone can help? Thanks!
Welcome to the club. No solution yet :/
http://forum.xda-developers.com/x98-air/help/touch-screen-fix-teclast-x98-air-iii-t3287435
Related
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?
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
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
I was running ARHD 20.1 with the latest 3.09 firmware and since i had terrible battery life i decided to downgrade . I asked in this same forum if there would be any issue and i was told there wouldn't.
So, today i downgraded to 2.24 firmware and then installed 3.06 GPE firmware. Next, i installed ARHD 3.2 GPE and did a full wipe before doing so. When it booted i got unfortunately com.android.phone has stopped working non-stop. I thought it was a problem with the rom so i re-downloaded everything and reinstalled wiping again but with no luck.
I started getting nervous and decided to downgrade to 2.24 to see if the radio was causing the issue but i still got the FC , i tried with all the firmwares with no luck. Last, i flashed back the 3.09 and got just 1 FC but then it stopped and it ran normally.
What is causing this issue? Did i mess up something by downgrading/flashing firmware too many times?
Im currently s-off and supercid.
Help is appreciated.
Thanks
Update : seems like my phone is completely fine on any sense based Rom but as long as I install any GE Rom the FC starts happening . Any ideas ?
Hi,
I have KLD6 unit. tryed some Malaysk 4.4.4 ROM and after 2 weeks of use the touch screen has started to not respond sometimes. Upgraded to Malaysk 5.1 and still the same.
Downgraded back to OEM 4.4. Was working fine for a week but now it still happening.
Sometimes restarting the unit works, sometimes not.
Sometimes I can use the unit for a while and than after some minutes of use it's not working anymore.
Physaical buttons are working fine all the time even when the touch screen isn't.
Anyone have an idea? Maybe a software issue? Incompatible app?
Thank you all
Chamuelm said:
Hi,
I have KLD6 unit. tryed some Malaysk 4.4.4 ROM and after 2 weeks of use the touch screen has started to not respond sometimes. Upgraded to Malaysk 5.1 and still the same.
Downgraded back to OEM 4.4. Was working fine for a week but now it still happening.
Sometimes restarting the unit works, sometimes not.
Sometimes I can use the unit for a while and than after some minutes of use it's not working anymore.
Physaical buttons are working fine all the time even when the touch screen isn't.
Anyone have an idea? Maybe a software issue? Incompatible app?
Thank you all
Click to expand...
Click to collapse
Happened to me. Reinstalled MCU firmware and that cured the problem... Don't ask why ROM is messing MCU but it looks like it happens... So just try flashing you original or latest MCU for your device type. Of course first carefully read info on how to do that and be sure to use right MCU for your exact HU type. And write down Factory Settings as they may be messed after MCU reflash. And final note: I would also recommend Factory Reset or Clean all data/cache after MCU flash.
pa.ko said:
Happened to me. Reinstalled MCU firmware and that cured the problem... Don't ask why ROM is messing MCU but it looks like it happens... So just try flashing you original or latest MCU for your device type. Of course first carefully read info on how to do that and be sure to use right MCU for your exact HU type. And write down Factory Settings as they may be messed after MCU reflash. And final note: I would also recommend Factory Reset or Clean all data/cache after MCU flash.
Click to expand...
Click to collapse
Hi,
Thanky you for the idea.
tried any public MCU for my HU.
2.83
2.85
2.91
Also tried couple of factory reset and wipes.
Noticed that the kernel has remaind the rooted one. Maybe that what causes the problem?