Hi folks,
I rooted my Transformer last night, I was running stock 3.2 rom.
After rooting I've installed Revolver 3.5 from CWM, everything went fine, I was thinking.
But I've noticed I can't rotate the screen anymore, I tried switching the auto-rotate on and off couple of times but nothing is happening.
I did factory reset prior to installation.
I even tried the latest Prime rom, again - no rotation at all.
Does anyone have the same issue as me?
R.
I've restored to original boot+recover+system and rotation is working ok again.
I guess rooting might messed up something.
R
Related
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
qaaqq said:
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
Click to expand...
Click to collapse
I have the same issue, only the position is different. Have you worked out a solution? Or still waiting for it? Anyone?
Im on Miui with matrix cfs 5.5 (9023)
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
bucimaci said:
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
Click to expand...
Click to collapse
I have this problem also, im on CM7 nightly. cant unlock the screen. Phones barely 3 days old
Had that same problem, and it's gone now. Don't know what did fix it, but I flashed new radio and Trinity kernel, and the problem is gone now...
I thought with the 2.3.5 the problem was solved, but its back now... dunno what it is, my phone is 2 weeks old.
I'm experiencing the same issue on a stock, not rooted or in any way modified Nexus S I9023 (SCLCD version) with Android 2.3.6
Also the settings button is right under the line (so the location is different from the video) and it is unresponsive as well.
Does anybody have any idea what to do about this???
so i initially was using prime 1.8 after flashing it with nvflash after rooting. then i flashed prime 1.9 and the green theme. i had made nands every day r so for a few days and everything worked fine. then i tried to restore a nand after flashing a systemUI tweak that i didnt like. i wiped everything first and the flash went fine, but after rebooting it keep bootlooping on the spalsh screen then turns off completely.. i had to use nvflash to get back into the system and re-flash the 1,8 prime system files.
now im on revolver 3.2 with clemy''s v18a kernel and everything seems to be working fine (just like it was before) i have made some nands, but havnt tried to restore any for fear of having to start all over again (i use my tab for school, and need a stable system).
any thoughts? any body else had any problems restoring nands?
My TFT touch screen is not responding until i lock the screen and unlock it again and sometimes it goes crazy and do like I have 1 finger on it
Tried Revolution HD and now I'm using Megatron 1.1.6 with guever's kernel
There's an app for that
Search for touchscreen booster in themes and apps. Also clean your screen, see if either of those help. If not try a total wipe and reflash of latest Guevor with a stock-based ROM, then move on to AOSP if it works fine.
If not... stock reflash.. if not.. hardware problem :/
Yes, I've tried with Touchscreen bootster but problem still there . Reflashed stock today and testing
My screen is seem like this http://www.youtube.com/watch?feature=player_embedded&v=d3_cpwfO5T8
until I lock and unlock screen or reboot, I can use it for about 1 hour and the problem happen again
Is your screen or Bezel out of place (longshot, probably not xD)? You could try a Honeycomb ROM and see if that'll fix it if it's software and worked beforehand.
Thanks for your help. I'm testing stock fw from Asus
Stock rom
No root
Happen 4~5 times a day have to sleep few time and wake it up to get it working
but the track pad is working/ OS is running/
Installed touch screen booster but no luck
But I didnt have this problem in Honeycomb
Last step, downgrade to HC and see ifit fixes.
My TF101 just recently started showing some wake issues, specifically a non-responsive touch screen and no wifi connection.
It is rooted and I installed a couple of custom roms and the KAT kernel.
First time noticing those issues was with the custom roms, so I decided to revert back to stock, with the backup I made. I also reflashed the stock kernel.
Does anybody have had these problems and knows how to fix them?
So ever since yesterday I've been able to use WiFi. I was chromecasting something and while it was casting my phone went through a reboot, thought nothing of it since its happened lately. Well i think it did it a few times. Well I check my phone after my show is over and my WiFi is off., and I can't turn it on. I rooted my phone last night since it was unlocked already from when I had it rooted before. It's on Android 6.0 right now. I was just wondering if anyone had any ideas of how to fix it. I was getting a logcat error in reference to the wifistatemachine.
Did you try flashing an older stock rom?
I have a phone with the same problem and it believe it is a hardware problem because stock and custom kk, lp, and M ROMs do not solve the problem. After swapping out the motherboard, everything was fine.
I have not yet. I was trying to create a nandroid backup first, but NRT doesn't seem to want to let me do that because i don't have a modified boot image.