Hi all, my Nexus has an issue with the rotation of the screen. I've done some googling and downloaded the check my android app. The sensors missing are 1, 3 and 5. I have tried the following:
1. Factory reset the device
2. Attempted the pressure press on the 'n' and 's'
3. Opened the tablet and tried the tape and cardboard fix
4. Reseated the cable that I understand controls the orientation
I've done extensive research on the problem but no luck.
None of these options worked. I have contacted Asus but I'm pretty sure my warranty is up. How can I fix this please?
Hi,
Temporary solution for me: reboot in safe mode and test if orientation sensor works. If it does, reboot again in normal mode and you'll be fine ... But only for some time, as in a day or two rotation failed again.
To boot into safe mode, long press power button until power off message appears on screen, then long press button on screen until boot to safe mode button appears.
Hope it helps!
My n7 does that as well,
Truthfully All I do to fix it is (yes restart but that is annoying), just rotate it to where you want it, and give it a firm, but soft tap along the side of the device.
I found it wakes up the sensors and allows them to operate again
Hope this helps
Hi. It's a fairly common issue with our Nexus7.
My rotation sometimes get stuck also, so i installed an app called "Adaptive Rotation Lock" and problem solved.
So I've tried the safe mode, no good. I also tried the soft tap, no good. Even using adaptive rotation lock does not work. I'm thinking this is a hardware issue. l will have to call ASUS as the email support was complete ****. Thanks for the help all the same.
Assuming you do not have the rotation lock setting enabled I think I have a solution for you.
I had this same issue and I literally tried for 3 months trying to fix it. I finally found some obscure website with a fix. It involved opening up your tablet and basically "securing" one of the cables. After I did that I have not had a rotation problem anymore.
http://blog.daum.net/enue81/2
I seen that in my travels and tried to implement the same fixes, as it is in Chinese or something similar I tried to interpret what he did.
I used black electrical tape to secure the cable ends, then used a similar tape to secure the cable down, unfortunately that didn't work but there's every chance I did it wrong.
Can you please explain what you used?
I've also tried following these two youtube videos:
I didn't use anything. I just basically "pushed" the cables in more even though they did not appear to be loose or anything. It definitely did the trick. YMMV though.
Related
Hi,
I decided to try out some new ROMS in general as I hadn't updated my phone in ages. I knew I wanted to try out the android version, so I tried the following steps:
1) updated my version of hardspl to 3.28 as the version I had was very old.
2) installed one of the official UK windows ROM to check out the latest vendor offering and update my radio before trying android. think it was the latest O2 one.
3) installed Myn’s Warm Donut to NAND
4 ) installed Incubus26Jc's Super Eclair to NAND
Now, I wanted to try some other windows roms, but cannot get to the tricolored screen. I have tried lots of times, several techniques, but no sign of the tricolor.
I read somewhere that installing an OEM ROM wipes out the hardspl. Is this what has happened? If so, is there a way to re-hardspl my phone from the sd-card (as I cannot make activesync connections anymore), or a way to install a windows-rom from the sd-card without going through the tricolor screen?
Any help you could offer would be greatly appreciated.
Best regards,
ET
As far as I am aware flashing a stock rom will not remove HardSPL, in fact I have flashed one of my kaisers with so many roms I have lost count, but never lost HardSPL, even with the latest generic HTC rom, which is pretty much the last word in stock roms as far as kaiser is concerned.
I'm not certain what has happened, but not getting the bootloader is, I'm afraid, very serious, if you have no access to the bootloader then it is very difficult to flash anything.
I'm going to have a good look around some wiki and forum pages, see what I can find out, in the meantime, can you confirm that you have something you can boot to? Even if it's android on nand then there may be some way of figuring out what has happened, and the hope of a fix.
From your post may I assume that all your attempts to get the bootloader ended with a normal boot of some sort?
Hi! Thanks for your very quick reply!
I can currently boot into android, with no probs and have a 2gb sd card I can access via an adapter on the pc.
I tried accessing the bootloader via holding camera and power down, then pressing reset for 3 seconds. also tried holding the buttons down for different permutations of time up to ~30-45 secs. no joy.
Also tried the battery out. put in battery. press power, then camera; or power and camera together.
Everytime I have tried it, i stay on the O2 logo, then the linux bootup stuff flies past.
I suppose the button assignments can't have been switched as the bootloader should be before any of the android stuff, right? Any advice would be greatly appreciated.
Button assignment can be changed after the OS has booted, but during boot they are hardcoded.
As long as it boots, then the bootloader is still there, and functioning, without a bootloader the phone would not boot at all, I'm actually wondering if the camera button has failed?
yeah, i was wondering about that too. is there a quick way to check within android? all the buttons are different from win. e.g red phone puts phone to sleep and of course there is no camera app to take photos in...
Well since you still got a working nand flashed you could install Warm Donut, camera works in that, however perhaps a simpler way might be just to press it gently, all the way in, if it is working correctly you should feel two 'click' positions, it's not always easy to diagnose hardware failures, but if the internal switch has broken/come adrift, you may be able to feel it.
ok, will try both & post back tomorrow. thanks for your help.
hmm... i think checking camera button in android is not possible because the camera app dont use the hardwarebutton. You have to press a button on screen to take a picture. You can check some buttons in linux bootup phase like the hardwarekeys on front. but not the camera button and the other sidemounted keys...
you can do this to test the camera button (in android):
- switch into text mode: fn + left softkey
- press camera button and tab somewhere on the screen
is there an output with s.th. like "TS-Calibration" then camera button is working
Hmmm, I don't think the camera button is working. During android boot up, all the hard keys output a character to the screen apart from the camera button. toastys suggestion did not yield a camera result either.
This makes sense, as I have tried a ridiculous amount of times to get to the tricolor screen.
has anyone got any ideas of how to load a windows rom back onto nand and bypass the botloader? If not, i guess my only option is to dismantle the phone in the hope that the non-functional camera button is due to a loose contact.
Thanks for the help guys.
No output = no camrea key i'm afraid, it does sound like either a fractured solder joint or something similar, not an easy repair, and yes it will require dismantling to get at the mainboard.
If you have the equipment then simply reflowing the solder joints on the switch should sort it.
As far as I'm aware there is no way to flash without access to the bootloader, however it might be possible to rig up a temporary camera switch using two pieces of thin rework wire, although I don't recommend it without previous experience of surface mount soldering
I'll let you know how it goes.
toasty_ said:
you can do this to test the camera button (in android):
- switch into text mode: fn + left softkey
- press camera button and tab somewhere on the screen
is there an output with s.th. like "TS-Calibration" then camera button is working
Click to expand...
Click to collapse
i tried this for fun. it caused bad calibration when i came out of text mode (fn + right soft key).
cool to find text mode though. that works fine
Hehe i tried this too.
For people who have bad calibration after this: You can fix it with "Dev Tools". Goto "Pointer Location" and you will see what exactly happen to your calibration when you touch the screen. To fix the calibration use the stylus, press & hold camerabutton and tip all corners of your screen clockwise. Begin with the topleft corner.
highcoder said:
Hehe i tried this too.
For people who have bad calibration after this: You can fix it with "Dev Tools". Goto "Pointer Location" and you will see what exactly happen to your calibration when you touch the screen. To fix the calibration use the stylus, press & hold camerabutton and tip all corners of your screen clockwise. Begin with the topleft corner.
Click to expand...
Click to collapse
Reboot also works. just thought others should know
Good afternoon all, I'm wondering if anyone can help.
My Galaxy Tab Pro 10.1 developed an issue with the screen (after travel - where it may have been knocked around a little)...
The tablet boots up fine and the screen appears to work normally.
However once the screen times out and switches off, or the screen is switched off by the power button, it is not possible to get the screen back on.
It appears that it's just the backlight that is not coming back on?.... as the screen responds to touch (you can here the pin code buttons being clicked).... but can't see anything at all on the screen.
Rebooting the tablet from here makes the screen come back on as normal - so as it works like this and just does not come back on after being 'on staandby' I thought it might be a software issue... I did a full factory reset but unfortunately the problem is still exactly the same.
I've had the tablet to bits to see if I could see any cables loose or anything - but everything looks ok - I think (Although it's the first time I've had one apart and wasn't 100% sure which cables were for the screen)
There was nothing obviously disconnected or loose.
Has anyone come across this fault before or can anyone provide any more guidance? Maybe a particular cable to check or how to check it?
Many Thanks,
Tom Leitch
I have the same issue, but I was able to fix it entering the factory mode and pressing the sleep button. That was possible using the calculator and entering (+30012012732+ and then entering *#0*# to get to test mode.
The problem now is that I'm using lineageOS so I don't know how to get to that menu or trigger that sleep button. Anyone?
Basically my issue is this:
If my phone is booted normally, and the screen turns off due to time out or me pressing the power button, I cant get it back on without a reboot.
Things i have tried:
- booting into download mode, recovery, and boot manager - When in any of these the screen works correctly. The power button works as expected.
- full rom wipe and clean install of a different rom + updated firmware - No change- Replacing the SD card+volume/power controls hardware - no change in behaviour- I have Vysor (an application for screen mirroring on PC and device control), when i use the button on it for turning the screen on/off, it shows correct behaviour of the mimicked screen on my PC.(i.e on/off wake/sleep). When i use the hardware power button Vysors mimic shows correct behaviour of on/off wake/sleep, even though the phone screen does not turn on.- I have tried disconnecting and re connecting the ribbon cable of the LCD, and tested with another LCD known to work - behaviour remained the same.
Summary:
- My phone is otherwise functioning correctly - confirmed using Vysor
- My phone screen works - confirmed using 2x phone screens
- My phone screen works in recovery, bootloader and download mode as expected
- My power buttons work - confirmed in each of the above
- My phone boots by pressing the power button just fine, and the screen comes on fine
- Digitiser functions all working as expected
- if my phones screen is on, I can turn it off with the power button just fine
-- I can not turn the phone screen back on without rebooting the device (I use ADB or Vysor to reboot), but the phone IS waking up (seen through Vysor)
Any ideas?
On the one hand, it really looked like a hardware issue to me at first, but the problem persisted through 2x screens and 2x power buttons, and the power buttons and screen work in all other situations.
This then made me think it was software, but i replaced the firmware, recovery, and changed rom, with a full wipe (except data) to no effect. (yes i am s-off, and have done the trick to get permissions over the other remaining items such as software status)
I am completely stumped on what to try next.
Any suggestions would be very much appreciated, I am not overly familiar with software specifics.
rukia06 said:
Basically my issue is this:
If my phone is booted normally, and the screen turns off due to time out or me pressing the power button, I cant get it back on without a reboot.
Things i have tried:
- booting into download mode, recovery, and boot manager - When in any of these the screen works correctly. The power button works as expected.
- full rom wipe and clean install of a different rom + updated firmware - No change
- Replacing the SD card+volume/power controls hardware - no change in behaviour
- I have Vysor (an application for screen mirroring on PC and device control), when i use the button on it for turning the screen on/off, it shows correct behaviour of the mimicked screen on my PC.(i.e on/off wake/sleep). When i use the hardware power button Vysors mimic shows correct behaviour of on/off wake/sleep, even though the phone screen does not turn on.
- I have tried disconnecting and re connecting the ribbon cable of the LCD, and tested with another LCD known to work - behaviour remained the same.
Summary:
- My phone is otherwise functioning correctly - confirmed using Vysor
- My phone screen works - confirmed using 2x phone screens
- My phone screen works in recovery, bootloader and download mode as expected
- My power buttons work - confirmed in each of the above
- My phone boots by pressing the power button just fine, and the screen comes on fine
- Digitiser functions all working as expected
- if my phones screen is on, I can turn it off with the power button just fine
-- I can not turn the phone screen back on without rebooting the device (I use ADB or Vysor to reboot), but the phone IS waking up (seen through Vysor)
Any ideas?
On the one hand, it really looked like a hardware issue to me at first, but the problem persisted through 2x screens and 2x power buttons, and the power buttons and screen work in all other situations.
This then made me think it was software, but i replaced the firmware, recovery, and changed rom, with a full wipe (except data) to no effect. (yes i am s-off, and have done the trick to get permissions over the other remaining items such as software status)
I am completely stumped on what to try next.
Any suggestions would be very much appreciated, I am not overly familiar with software specifics.
Click to expand...
Click to collapse
It's a costly experiment in way of time and effort, but it may be worth going completely stock with a RUU. Assuming a backup of your data & settings you won't lose anything - and you might rule out the software issue (I'm thinking maybe you've gotten unlucky with the ROMs and/or kernels you've chosen, but possibly an app as well).
computerslayer said:
It's a costly experiment in way of time and effort, but it may be worth going completely stock with a RUU. Assuming a backup of your data & settings you won't lose anything - and you might rule out the software issue (I'm thinking maybe you've gotten unlucky with the ROMs and/or kernels you've chosen, but possibly an app as well).
Click to expand...
Click to collapse
Cheers for the suggest, not sure why i didnt think of that... think my mind was subconsciously blocking out that option.
So, i flashed the RUU for my 401 device from Flippys collection, and I still have the problem.
if everythings stock and i have the issue, I guess it must be hardware.
My Zenfones away getting fixed though so ill just have to struggle along with this somehow.
rukia06 said:
Cheers for the suggest, not sure why i didnt think of that... think my mind was subconsciously blocking out that option.
So, i flashed the RUU for my 401 device from Flippys collection, and I still have the problem.
if everythings stock and i have the issue, I guess it must be hardware.
My Zenfones away getting fixed though so ill just have to struggle along with this somehow.
Click to expand...
Click to collapse
I'm plumb out of ideas - I agree that it probably is a hardware issue, maybe something to do with the motherboard itself? I'm sorry.
My 2013 LTE N7 will not turn on from a fully off state with the power button(I use Wugs Toolkit to turn it on). It also will not "screen on" or "screen off" when on the home page. If you are in ANY app, the button works fine for turning the screen on/off.
I have done several hard resets, I have flashed several different versions of Android through Wugs Toolkit, tried booting in safe mode, replacing the power button assembly, everything I can think of...still, no workie...
The only thing I can think of I haven't tried, is a custom ROM. If I can't get any help here, it will be my next attempt.
The only other issue I have noticed is the auto screen rotation doesn't work all the time(seems to be working just fine right now?), but, it does change when I choose an app that is portrait or landscape specific. This issue is intermittent, but not near as big of a deal as the power button issue.
I fancy myself a fairly technologically knowledgeable guy, and I like to rebuild broken phones and tablets that I buy off eBay. I have come across lots of issues and thought I had seen just about everything, but I am stumped. Any help is greatly appreciated.
Thanks,
could
I have a Samsung I9250 which I've unlocked, rooted and loaded with Lineage. The Lineage version is 13.0-20171126-NIGHTLY-maguro. The recovery is TWRP and the root is through SuperSU FREE (CM) v2.79-SR3. The On/Off button doesn't usually work. If the phone is off then pressing On/Off has no effect. Occasionally it works for no reason I can see, it seems to be random, but for the most part it simply doesn't have any effect. If the phone is on then the same is true. Turning it off from the On/Off button is usually impossible. I get round this through Settings>Display & lights>Wake on plug. This means I can activate the phone by connecting it to a PC using its USB cable. This will activate the phone immediately if it is off. It doesn't help with turning it off and I am usually reduced to taking the battery out. The phone is effectively useless although it is clearly NOT bricked. When I can turn it on it works fine.
I don't know if this is a hardware or software problem. If it's a software problem I don't know if the fault is in Lineage or TWRP or SuperSU. I noticed that the problem existed before I installed SuperSU. Has anyone else come across this problem? I'm reluctant to bin the phone because I spent such a long time getting Lineage on to it, but, if I can't turn it on or off it's not really a phone. Any help would be greatly appreciated.
@erich_vogt it's more a hardware problem, you can buy a new button (find link of online stores in accessories section or google.it).
for easyness you don't need to plug charge/usb everytime, you can set volume button waker, find in settings > button (don't remember where correctly, it will be somewhere there) then use volume switches to wake it.
erich_vogt said:
If the phone is off then pressing On/Off has no effect.
Click to expand...
Click to collapse
There have been power button bugs, but only in the OS. If it's not turning on from off, then I think the switch is broken! A common failure in old phones, which is why "volume button to wake" is important, to reduce load on the power button.
Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.
erich_vogt said:
Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.
Click to expand...
Click to collapse
3rd dec nightly has problem with booting, get back to older than it.
Reset volume button waker, if it stopped working. I never had problems with volume buttons.
I'd second the idea of it being software. I've had problems with all builds after 20171112. I get the impression there was something overlooked when the developers unified the builds for different GNex variants.
If you still have the phone, try that 20171112 build.
I don't know how to roll back to an earlier build. The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.
erich_vogt said:
The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.
Click to expand...
Click to collapse
Ah, ok. Sorry, I thought you could still do more than that, but it was rebooting and unusable in that sense.
That's well beyond any help I can offer you. I hope you got any data off it.