Hi,
if I'm long-pressing my power button to open the screenshot and shutdown menu, it often fails because the display goes off (seems like the system would recognize it as a normal click).
Sometimes it's worse than other times, at least I think so. I didn't upgrade to Android 5 until now (mainly, because it does not work ("Update not possible"), but that's a different topic).
I wanted to ask for your opinion, if this is rather a software or hardware related error and what could possibly cause it?
Thanks and best regards,
Felix
Related
Hi,
I wonder how the power-off functionality of the ARTEMIS works. Is it a kind of software functionality or does it do the power-off through hardware?
With other words: Is it possible to deactivate complete power-off through an application, i.e. through capturing the message of the power-off key pressed?
(I'm talking about holding the key for a couple of seconds which causes powering off the device after a confirmation screen).
Kind regards,
ma_gu
An interesting question.
I'd like to know it too...
My Touch Pro 2 kept reverting to the TouchFlo home screen within a couple of seconds of opening other applications (eg. click on a new email, and a second later it goes to TouchFlo. Soft resets didn't make any difference: nor did disabling TouchFlo (from the Settings/Today/Items menu) - it then just reverted to the Windows home screen instead. So I tried to hard reset the machine. I read that the way to do it is to hold send+end+power, but that didn't do anything. Some posts suggested that volume down+reset was the way to do it, so I tried that. I've now got a tricolour screen, which starts:
RHOD100 32M MI-BC
SPL-0.84.0000
A bit more searching suggests that this is the bootloader (?) screen that comes up when you want to flash a ROM, and I feel dangerously close to doing something expensive and irreversible. Any suggestions as to how to get out of this screen? Nothing obvious when I search the forums here. I was thinking of just taking out the battery. And any thoughts on how to hard reset - or how to stop deal with the original problem?
Thanks
You ain't going to mess anything up. You can flash a new rom from there though but there is no way to do it by accident. Don't you hard reset by holding down the green and red call buttons and soft reseting? I remember it being different from the Touch Pro 1.
you might head over to the rom section, read up on the "flashing your phone for the first time" thread. Answer is most likely in there.
Thanks for coming back so quickly guys. The ROM flashing thread didn't explain how to get out of the tricolour screen. Meanwhile I just took out the battery and that did the trick. I still couldn't hard reset using the send+end+power buttons as instructed here and in the manual. I was able to get to the Settings/System/Clear Storage menu and was eventually able to keep it open for long enough to enter "1234". That hasn't dealt with the original problem, though - switching back to TouchFlo after a couple of seconds in each application. It's also beeping incessantly. Any ideas?
It sounds like your device is registering a phantom End key press every couple of seconds. That would explain it popping you out to the home screen and the beeping. If your End key is indeed acting weird, that would also explain why you can't hard reset using the power+send+end key combination.
You should send it in for warranty replacement...
ohyeahar said:
...registering a phantom End key press every couple of seconds...
Click to expand...
Click to collapse
That makes a lot of sense, thanks. Now that you mention it I realise that it's the same kind of beep and the same result as the End key.
I've only had it for 2 months. I'll get on to HTC.
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
Hi all,
I've had some problems with my S3 power button. It's behaving like it's being pressed when it isn't. Just slightly brushing it, without depressing the button, is registering a press. Pressing the button is behaving like the button is being held.
I've read a number of possible fixes. I tried software options, just to be sure (cleared cache, factory reset). But this is almost certainly a hardware problem.
I stripped the phone down and the physical button itself looks absolutely fine. It is interacting as it should with the internal button on the motherboard. The issue seems to be that the internal button attached to the motherboard (the little white button) is registering clicks even when it's not being fully depressed.
The phone did have some water damage about 6 months ago. I wonder if this could be causing the the phone to mess up now?
I even tried a fix that many people seem to think works: smacking the crap out of the power button itself. It had no affect on my phone - I think that "fix" that is for a power button that is stuck depressed and not a power button registering phantom clicks/being hyper-sensitive.
So I suppose I have the following questions:
1) Has anyone else experienced similar problems and, if so, did they get it fixed?
2) My plan is to try replacing the motherboard/logic board and see if that helps. Does that sound like the best fix or is it overkill?
3) If I'm replacing the motherboard, does it need to be an I747 motherboard or will any S3 model work fine?
4) What's the best source for a motherboard? I don't mind if they're used or refub so long as they work.
Any advice you can offer is welcome.
Cheers.
BenScopato said:
Hi all,
I've had some problems with my S3 power button. It's behaving like it's being pressed when it isn't. Just slightly brushing it, without depressing the button, is registering a press. Pressing the button is behaving like the button is being held.
I've read a number of possible fixes. I tried software options, just to be sure (cleared cache, factory reset). But this is almost certainly a hardware problem.
I stripped the phone down and the physical button itself looks absolutely fine. It is interacting as it should with the internal button on the motherboard. The issue seems to be that the internal button attached to the motherboard (the little white button) is registering clicks even when it's not being fully depressed.
The phone did have some water damage about 6 months ago. I wonder if this could be causing the the phone to mess up now?
I even tried a fix that many people seem to think works: smacking the crap out of the power button itself. It had no affect on my phone - I think that "fix" that is for a power button that is stuck depressed and not a power button registering phantom clicks/being hyper-sensitive.
So I suppose I have the following questions:
1) Has anyone else experienced similar problems and, if so, did they get it fixed?
2) My plan is to try replacing the motherboard/logic board and see if that helps. Does that sound like the best fix or is it overkill?
3) If I'm replacing the motherboard, does it need to be an I747 motherboard or will any S3 model work fine?
4) What's the best source for a motherboard? I don't mind if they're used or refub so long as they work.
Any advice you can offer is welcome.
Cheers.
Click to expand...
Click to collapse
I had the exact same problem with mine, and unfortunately there's not much you can do about it as it's a hardware defect. I haven't tried replacing motherboards or anything, so that might help you. What I did to help with the problem was rerouting my power button to my volume up key so that I can use the power button as little as possible. The only time I use the power button now is when I need to power it on - which causes reboot loops sometimes.
Drisc0 said:
I had the exact same problem with mine, and unfortunately there's not much you can do about it as it's a hardware defect. I haven't tried replacing motherboards or anything, so that might help you. What I did to help with the problem was rerouting my power button to my volume up key so that I can use the power button as little as possible. The only time I use the power button now is when I need to power it on - which causes reboot loops sometimes.
Click to expand...
Click to collapse
Sucks.
I like the sound of your work around, though. Was it pretty simple rerouting the power button?
BenScopato said:
Sucks.
I like the sound of your work around, though. Was it pretty simple rerouting the power button?
Click to expand...
Click to collapse
Ditto, my power button is borked too. Ended up doing the same thing but I don't use my power button at all. I just use rom toolbox to reboot system/into recovery
Rerouting was simple for me as it's baked into the settings in the rom I'm on (ground zero) as it is with most custom ROM'S I've been on. If you're just running stock I'm sure there's an app in the market that'll work however I'm drawing a blank ATM
Sent from my SAMSUNG-SGH-I747 using Tapatalk
brianray14 said:
Ditto, my power button is borked too. Ended up doing the same thing but I don't use my power button at all. I just use rom toolbox to reboot system/into recovery
Rerouting was simple for me as it's baked into the settings in the rom I'm on (ground zero) as it is with most custom ROM'S I've been on. If you're just running stock I'm sure there's an app in the market that'll work however I'm drawing a blank ATM
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I'm running CM.
I've had a look through the routing options. What I can't locate is a way to disable the power button completely. My main problem right now is the phantom clicks. I'd rather that button be dead.
Anyone know of a way I can make that happen in CM?
Nevermind. I just physically removed the power button. That did the trick.
For anyone interested, you can replace a faulty power button on the motherboard pretty easily and the parts are cheap. If I wasn't due an upgrade in 4 months I'd probably do that. No need to replace the whole motherboard.
Does anyone know the app to reroute the button? I too have the same problem.
My OnePlus 3 appears to have developed an intermittent fault with the power button.
For the past week, I have found that a short press to the power button will not always turn the screen on or off as it should. A slightly longer press usually works, but it is difficult to avoid getting the power menu, or opening the camera instead. I am running the latest Lineage 15 nightly build (20181023). I tried rolling back to an older build but it made no difference.
Has anyone else seen a similar problem? How easy would it be to fix?
My insurance company has offered me a Samsung galaxy S7 edge or a Sony expera XZ as replacements instead of a repair. (They where not clear on the exact model or spec of either). Are either of these phones any good for rooting, alternative ROMs and the like?
Thanks.
Update to add: The power button has now stopped working completely. I guess this means that if the battery ever goes flat then I won't be able to turn the phone back on again without repairing it.
I also found an iFixit guide on how to replace the affected components and a vendor selling the parts. I guess this means that this is a fairly common problem.
https://www.ifixit.com/Guide/Oneplus+3+Power+&+Volume+Button+Flex+Replacement/76019
I have the same problem. Seems very common.
Hello, adding some info for people whose power buttons have given upp and find this thread:
I've lived without a functioning power button my OP3 for over a year now and it barely bothers me anymore.
First off: To turn on the phone plug it in to a computer while pressing the volume down-button. You're now in recovery mode and can choose "reboot into fastboot" from the menu. When in fastboot, open terminal on the computer and run fastboot reboot (you can find guides for setting up adb/fastboot here on xda, just google)
There's one thing to note here, I think you have to have at a earlier point connected the phone and the computer and chosen "always trust this device" for you to be able to run the command. I'm also not sure if you need to have unlocked bootloader previously.
To lock the phone during daily use, I use nova launcher which has "screen lock" as an action, I've added it as a "swipe action" for the app drawer-icon.
But in general, just make sure the phone doesn't die, keep a power bank and maybe up the power-save setting to start at 20%. It's quite aggressive and with power save + flight mode my phone has survived over 24 hours on 10% battery.