I've installed 2 JB ROMS on my Gamsung galaxy S i9000
When I unlock the phone, some random touch or gestures are generated, without touching the screen. It looks like the phone is cursed.
I press the power off button to lock it, and when I unlock it, it all works well again.
It seems like there is a bug in the touch driver as it didn't happen in my previous Gingerbread ROM. I have tried to go back to GB again to validate and it works well. As soon as I get JB, then it starts doing that.
It only happens after unlocking. If it doesn't happen straight away when I unlock it, then it doesn't happen.
I have tried already 2 Jelly bean roms and they all seem to have the same problem, so I guess it's in the main source code as they both are coming from the same JB source.
Happening in
[ALPHA][ROM][4.1.1] CyanogenMod 10 for Samsung Galaxy S
[ROM] Helly_Bean [4.1.1], based on sources of cm10
Anybody has had this issue?
I had that when I was in a hurry but just one time.
robertical said:
I've installed 2 JB ROMS on my Gamsung galaxy S i9000
When I unlock the phone, some random touch or gestures are generated, without touching the screen. It looks like the phone is cursed.
I press the power off button to lock it, and when I unlock it, it all works well again.
It seems like there is a bug in the touch driver as it didn't happen in my previous Gingerbread ROM. I have tried to go back to GB again to validate and it works well. As soon as I get JB, then it starts doing that.
It only happens after unlocking. If it doesn't happen straight away when I unlock it, then it doesn't happen.
I have tried already 2 Jelly bean roms and they all seem to have the same problem, so I guess it's in the main source code as they both are coming from the same JB source.
Happening in
[ALPHA][ROM][4.1.1] CyanogenMod 10 for Samsung Galaxy S
[ROM] Helly_Bean [4.1.1], based on sources of cm10
Anybody has had this issue?
Click to expand...
Click to collapse
Be sure you don't have the phone connected to a USB3 port when trying that.
I've only seen that happen in that situation.
Sent from my GT-I9000 using xda premium
pmos69 said:
Be sure you don't have the phone connected to a USB3 port when trying that.
I've only seen that happen in that situation.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
It happens randomly and without being connected to the USB at all.
As soon as I press the power button and I unlock it again it works well for the rest of the time I'm using it.
It seems that it could be related to the initialization of the touch driver or the screen.
Never happened in GB.
robertical said:
It happens randomly and without being connected to the USB at all.
As soon as I press the power button and I unlock it again it works well for the rest of the time I'm using it.
It seems that it could be related to the initialization of the touch driver or the screen.
Never happened in GB.
Click to expand...
Click to collapse
Same here
Have you found a solution now??
I have the same problem but in my case it happens when my phn is charging with blackberry charger when i unplugged it, it becomes normal..
Mayby try Elite JB RC12 (4.1.1) / JRO03L. This is not CM10.
eugenbljed said:
Same here
Have you found a solution now??
Click to expand...
Click to collapse
I installed GB Alliance JW6/ Semaphore and problem solved.
It works just as fast and it's got less problems.
Related
It's a very odd one in landscape they light up, in portrait mode they don't. Well, when I noticed that problem I immedeately flashed framework-res.apk - didn't fix so I remembered when I went to recovery they did light up, so did I and started counting seconds while it loaded into it but they didn't light up. So is this some kindo of physical damage? Landscape uses obviously different LED's, it ruins the niceness from that phone, when bottom bar is dark At the moment i was using Nik's Trinity 2.0 rom and i'm using it so far.
Can you guys provide some help, it will increases my love to the phone substantially.
Therefore my phone will be shiny and elegant again!!
I don't think you need to worry that it's a physical damage... If that was the case landscape buttons would be dead aswell. I wish I could help you but why not just flash an official rom and start over? I think running an HTC rom should fix the buttons at least...
owziee said:
I don't think you need to worry that it's a physical damage... If that was the case landscape buttons would be dead aswell. I wish I could help you but why not just flash an official rom and start over? I think running an HTC rom should fix the buttons at least...
Click to expand...
Click to collapse
Yes I would agree that you need to try a stock HTC ROM before you blame it on the hardware.
tpbklake said:
Yes I would agree that you need to try a stock HTC ROM before you blame it on the hardware.
Click to expand...
Click to collapse
Yes, but they worked in recovery earlier
henrylife said:
Yes, but they worked in recovery earlier
Click to expand...
Click to collapse
When you boot in recovery, it is not using the custom kernel that your ROM is using. In order to rule out hardware, you need to check the phone using the stock HTC IncS kernel and a stock ROM.
Installed CM 7.1 nope didn't work and tried a load of kernels...
So how do i take that apart?
henrylife said:
Installed CM 7.1 nope didn't work and tried a load of kernels...
So how do i take that apart?
Click to expand...
Click to collapse
get back stock to test whether it is working,cm7 wasn't stock though..
Sent from my HTC Incredible S using Tapatalk
Don't lose root.... newest stock will up date your h-boot
I don't want to know to stock I know how these lights work. They depend on framework-res.apk and on kernel. Ok well stock may change but it's 5% reasonable. Is there some kind of diagnostic tool out? A fastboot one will be great.
UPDATE: 2 days ago I used my phone as router and it was charging, so yesterday I did disconnect my phone and saw lights worked. While in bus they started blinking
(like dying bulb) and few minutes ago i barely saw them and then everything was dark again. Sometimes they get revived for some time and process is under loop again
I'm trying to remember, it occured after attempts to get it charge, Incredible S usb dock doesn't work properly so i crumpled it a little bit and finally it turned on. First notice were the lights, and after heavy charge they got somehow revived. I want to see this panel with my own eyes, can someone put disassemble guide please?
I'm pretty sure new backlit is quite expensive but unfortunately Physical damage it is.
It should be ROM's problem?
Maybe flash another ROM or restore stock ROM.
uggies said:
It should be ROM's problem?
Maybe flash another ROM or restore stock ROM.
Click to expand...
Click to collapse
Nah, it shouldn't
I think that my phone is not working completely after i flashed the 4 ics roms.Probably it was because of the hardware accerleration in the ics rom because after i tested out the roms and flashed back to gb roms,strange problems have appeared(the phone completely does not respond for 2 seconds).Its not the problem with the gb roms as i flashed zeus,cm7,miui,lezo roms and still have this problem.Im wondering if anyone have experienced this problem and if anyone knows how to fix this problem,PLEASE HELP !
zyfkurmom said:
I think that my phone is not working completely after i flashed the 4 ics roms.Probably it was because of the hardware accerleration in the ics rom because after i tested out the roms and flashed back to gb roms,strange problems have appeared(the phone completely does not respond for 2 seconds).Its not the problem with the gb roms as i flashed zeus,cm7,miui,lezo roms and still have this problem.Im wondering if anyone have experienced this problem and if anyone knows how to fix this problem,PLEASE HELP !
Click to expand...
Click to collapse
There's currently no hardware accerleration in the ics roms.
http://forum.xda-developers.com/showthread.php?t=1448803
Do this, and your problems should be solved.
After I flashed miui 2.3/ics (I can't remember) my kernel logo is visible for 15 seconds, so the boot process is much longer.
cakebomb said:
There's currently no hardware accerleration in the ics roms.
http://forum.xda-developers.com/showthread.php?t=1448803
Do this, and your problems should be solved.
After I flashed miui 2.3/ics (I can't remember) my kernel logo is visible for 15 seconds, so the boot process is much longer.
Click to expand...
Click to collapse
wtf.....................i think you don't understand my question.I did not brick my phone , it can boot up as normal , just that the phone does not function properly.It just doesn't respond for 2 seconds and then goes back to normal but it happens all the time so im getting frustrated.Don't know if anyone has a solution to my problem....Thank you for responding anyway
I understand your question.
So, if you do this procedure, you phone will be completly restored. (No more SU, Root, CWM etc.)
Then you can completly screen out/exclude software errors.
And if this not works, it's a hardware problem.
cakebomb said:
I understand your question.
So, if you do this procedure, you phone will be completly restored. (No more SU, Root, CWM etc.)
Then you can completly screen out/exclude software errors.
And if this not works, it's a hardware problem.
Click to expand...
Click to collapse
err..............the first thing that i did after i found out the problem was flashing with smartflash and i did it many times.Think its a hardware problem then.But i did not drop it on the floor or did anything like that , not sure what is the cause of the problem.D:
Have you experienced overheat while on ICS ?
Vinzgore said:
Have you experienced overheat while on ICS ?
Click to expand...
Click to collapse
when i use the phone or play games more than 7-10 minutes , it gets hot.
blue screen error
after flashing to ics ,after 3 to 4 hrs of usage blue screen error and CWM not working the error is, its showing an error occured while attempting to run privileged commands !!!
I have happen to see that blue screen that you mentioned but no strange things going on over here, and I have been flashing to ICS and restoring to GB all weekend just to compare. I know it may sound as a silly question but did you do your wipes before all those roms you mentioned?
As we all know by now the official 4.3 came out for the xperia T which was de and rooted, i installed it on the my xperia tl following the step by step instructions on the thread, everything works smooth for a while until the screen standby. when it does and im trying to unlock the phone the touch doesnt respond, i press the power button and tired again still nothing, pressing the power button several times and then the screen start pressing random things on its on activating and deactivating settings task bar is being pulled down etc then the touch start working and im able to use the phone until the screen time out and it happen all over again. i switch back to the 4.1.2 and i have no problem at all with it but im jus curious has anyone of the tl users experience this problem and is there a bug for us on the 4.3 and or if there is a solution ? please help me cause i love the 4.3 but hate the problem i have with it
Umm I had the same problem using the leaked version.. Since I'm using the official one I haven't had the problem.
What helped for me was to power off the phone using power and volume up buttons
St.Jimmy90 said:
Umm I had the same problem using the leaked version.. Since I'm using the official one I haven't had the problem.
What helped for me was to power off the phone using power and volume up buttons
Click to expand...
Click to collapse
i tried all that .. i also wipe cache and those other things . are u using a TL also?
No Xperia t
i need to know if any TL users are having this problem
I'm on a TL with official 295...everything works for me like it did on 4.1.2
Sent from my LT30at using xda premium
Did you try if reinstalling solves your problem?
St.Jimmy90 said:
Did you try if reinstalling solves your problem?
Click to expand...
Click to collapse
i tried everything i did it over from the begining with a stock 4.1 firmware from att and then root install cwm 8 wipe cache and factory reset and wipe the dalvik install rom and then update superuser right after . then reboot . when it loads it works perfect for the first few mins then something got activated and thats it the screen jus went crazy it start jumping and touching all over the place and then stop .
My Xperia T has same problem. Maybe because i took the screenprotector off and the touch screen is a bit damaged by it now?
silasje1 said:
My Xperia T has same problem. Maybe because i took the screenprotector off and the touch screen is a bit damaged by it now?
Click to expand...
Click to collapse
i dont think the screen protector has anything to do with it because i would have had the same problem when im on 4.1.2 because i did remove my factory installed sony screen protector aswell. i really believe its the firmware or module or drivers .what ever it uses to control the touch
i think i might find the problem, well atlease for my device ... my usb port is acting up when ever i plug it in anything wall charger or pc is freezes and i also disable to slide to unlock and set time out to 10 mins .. idk if this works for anyone else but ive been on it for 30 mins now and nothing has gone wrong so far
I must confirm that removing the screen protector makes the screen touches working a little bit worse, because the glass gets easier oily. It's even more worse, when usb charging is connected. Cleaning the glass makes it better again.
No issues
http://forum.xda-developers.com/showthread.php?t=2647459 Flashed this via cwm 6. Read the whole thread first. CWM 8 has been reported buggy by the DEV. Flashed from rooted stock 4.1.2 AT&T TL bond
gpgon said:
http://forum.xda-developers.com/showthread.php?t=2647459 Flashed this via cwm 6. Read the whole thread first. CWM 8 has been reported buggy by the DEV. Flashed from rooted stock 4.1.2 AT&T TL bond
Click to expand...
Click to collapse
i didnt know 8 was buggy i thought it was most stable .. ill try 6 .. thanks
i tried 6 .. its the same s**t so im done with this im jus gonna go back to 4.1 i cant deal with this anymore ive been trying for days to get this to work properly and its not like im a complete noob cause i came from the x10 so im quiet familiar .. so thanks for all ur help guys but im done with this
Hi all,
So I have an S3 i9305 sitting around doing nothing. Thought I'd play with it. I had and older build of Miui running on it fine.
Decided to put on CM11, and that's when my issues started. The phone boots, but as soon as I get to any sort of setup screen I can touch anything on the screen. The physical buttons work fine, but the screen isnt.
I flashed a touch CWM and TWRP, both of which loaded fine by I couldnt touch anything.
I flashed back to stock kernel and stock rom
Kernel from - http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265
ROM from - http://forum.xda-developers.com/gal...5/roms-updated-17-08-2013-pre-rooted-t1942150
Still unresponsive touch.
Anything else I can try before I write this off as bricked
Thanks!
pieinthesky10 said:
Hi all,
So I have an S3 i9305 sitting around doing nothing. Thought I'd play with it. I had and older build of Miui running on it fine.
Decided to put on CM11, and that's when my issues started. The phone boots, but as soon as I get to any sort of setup screen I can touch anything on the screen. The physical buttons work fine, but the screen isnt.
I flashed a touch CWM and TWRP, both of which loaded fine by I couldnt touch anything.
I flashed back to stock kernel and stock rom
Kernel from - http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265
ROM from - http://forum.xda-developers.com/gal...5/roms-updated-17-08-2013-pre-rooted-t1942150
Still unresponsive touch.
Anything else I can try before I write this off as bricked
Thanks!
Click to expand...
Click to collapse
1 more thing...get the RIGHT firmware from HERE - get the one for your country.....flash that and do a factory reset after it..and wipe cache....
happened to a friend with galaxy ace....but phone was back to normal after flashing stock firmware from samsung.
Thanks mate!
So I tried some more flashes, no luck.
Took the phone to the local repair place, they told me the screen is broken. They attached a different temp screen and it worked. They attached my screen to a different phone and it didn't work.
Quoted me $189 to replace the screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
Im sure i flashed wrong kernel.
Enviado do meu GT-I9300 através de Tapatalk
SnowPluralism said:
Im sure i flashed wrong kernel.
Enviado do meu GT-I9300 através de Tapatalk
Click to expand...
Click to collapse
Dont think so... tired a few from the SamMobile site with no success. The setup screen shows up fine - but cannot continue with the setup as I cannot touch the screen.
pieinthesky10 said:
Dont think so... tired a few from the SamMobile site with no success. The setup screen shows up fine - but cannot continue with the setup as I cannot touch the screen.
Click to expand...
Click to collapse
so it is a hardware problem....not software - you can flash whatever you like...won't solve it...
if you like the phone consider repairing it...
spiderman07 said:
so it is a hardware problem....not software - you can flash whatever you like...won't solve it...
if you like the phone consider repairing it...
Click to expand...
Click to collapse
Thanks for your help
I am having the same problem.
Even after installing new firmware.
The phone boots, screen is working. But the touch is not responding... I also did a factory reset + wipe cache.
Before that it was on CyanogenMod (4.2.2) and the screen was working properly.
What else can I do TT ?
I changed the front panel.
And it is working perfectly well...
How can modification to the software affect the hardware and brake the digitizer/touch function ?
via kernel man...kernel is the interface between software and hardware....
maybe a frequency or voltage got changed by kernel and something happened....no one can know for sure...
gidam said:
I changed the front panel.
And it is working perfectly well...
How can modification to the software affect the hardware and brake the digitizer/touch function ?
Click to expand...
Click to collapse
When wrong kernel is flashed, the touch sensor get disconnected and unrecongnised by the phone. Thats why the hardware is broken even though correct kernel is flashed afterwards. Best thing to do is replace the screen instead of trying over and over again.
Hope it helps
I use the Samsung GT 19305 LTE myself.
I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Maybe there's a problem on your phone's battery. Try to bring it on a service center.
error01671 said:
I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Click to expand...
Click to collapse
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
paul c said:
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
Click to expand...
Click to collapse
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
error01671 said:
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
Click to expand...
Click to collapse
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
paul c said:
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
Click to expand...
Click to collapse
OK, I got some conclusions, and it might be a hardware problem.
First, I replaced the battery with same ROM, it still got SOD.
Then I flash Omni, PAC, Euphoria-OS, all got SOD like before.
So I return to MIUI, no SOD, but I got random reboots and sometimes Wi-Fi will disconnect itself even in its range.
Now I'm using Ivan's AOSP, still got random reboots and Wi-Fi problem.
And now I need this phone to work because I don't have a backup, waiting for new Nexus!!