I have searched everywhere for a solution to this problem and trust me, the search button has never had this many presses before
I have a HTC HD2 and 'almost' everything works, but there are a few issues I have.
I'm not a noob in ANY sense and I always try and find a solution to my problems before posting about them, that is IF I can't solve the problems myself
First off, this is my current setup for the HD2:
HD2: International 512mb HTC HD2
Radio: 2.15.50.14
HSPL2.08
MAGLDR V1.13
Recovery: MAGLDR CWM Recovery v3.0.2.4
Current ROM: NexusHD2 JellyBean CM10.1.3 V2.7 by Tytung
Previous ROM: PACman HD2 v1.2a by Xylograph
Kernel: tytung_jellybean_r2
Ok, the problems. What are they?
First off, the phone will NEVER, and I really mean NEVER, enter Deep Sleep. Deep Sleep is always amongst the unused CPU states. I have tried everything to get it to go to Deep Sleep to no avail. I tried another ROM to see if the ROM/kernel was at fault, but it isn't. They all have that problem. There are no apps that are causing wake-locks and even using an app that forces Deep Sleep will not work. The lowest the CPU will go is 96Mhz and never below it. I have the Max CPU speed set to 1190Mhz and the lowest set at 96Mhz. I also can never confirm a time when Deep Sleep did work, because it never did
Second problem, the physical buttons on the device act very erratically. I don't have the well-known power button issue, but I have something similar. The power button doesn't work on a long-press. If you long-press the power button it should give you the power menu, right? In my case, that never happens. What will happen is the display will turn off, as if I simply pressed and released it, like when you lock the phone. No matter how long you hold it in, the power menu will never appear.
Other buttons also act odd. The volume down button does work, but it also triggers the multitasking window to appear, every time I press it. This behaviour is not restricted to being in Android. Scrolling in CWM with the volume rocker, because that is the only way you can navigate this version of CWM, also does this. The log window will disappear and re-appear constantly, but sometimes it doesn't do this. This problem is only with the volume down button. The volume up button works just like it should. Other buttons do give problems, but they are not ever-persistent like the ones I mentioned above. The others just have constantly changing behaviour. They will perform different tasks at random when pressed, like open the dialer, or go home, or open the multitasking window as well, or even go back sometimes.
Now, I don't know what happened to Tytung on XDA, nor do I want to find out because it isn't important to me, but I'm not trying to advertise his work. I'm just trying every ROM I can find.
The phone does have water damage, but that was many years ago. No repairs were done to it, but it still works just like it should. The only problems are the ones I mentioned above. I do think that the water damage did do something to the buttons of the phone, but is it even possible that Deep Sleep can be affected by this? Isn't Deep Sleep something that is software-based?
I really would like to know what the is going on here
Any help would be greatly appreciated
I hope I provided enough information about this problem
D395267 said:
I have searched everywhere for a solution to this problem and trust me, the search button has never had this many presses before
I have a HTC HD2 and 'almost' everything works, but there are a few issues I have.
I'm not a noob in ANY sense and I always try and find a solution to my problems before posting about them, that is IF I can't solve the problems myself
First off, this is my current setup for the HD2:
HD2: International 512mb HTC HD2
Radio: 2.15.50.14
HSPL2.08
MAGLDR V1.13
Recovery: MAGLDR CWM Recovery v3.0.2.4
Current ROM: NexusHD2 JellyBean CM10.1.3 V2.7 by Tytung
Previous ROM: PACman HD2 v1.2a by Xylograph
Kernel: tytung_jellybean_r2
Ok, the problems. What are they?
First off, the phone will NEVER, and I really mean NEVER, enter Deep Sleep. Deep Sleep is always amongst the unused CPU states. I have tried everything to get it to go to Deep Sleep to no avail. I tried another ROM to see if the ROM/kernel was at fault, but it isn't. They all have that problem. There are no apps that are causing wake-locks and even using an app that forces Deep Sleep will not work. The lowest the CPU will go is 96Mhz and never below it. I have the Max CPU speed set to 1190Mhz and the lowest set at 96Mhz. I also can never confirm a time when Deep Sleep did work, because it never did
Second problem, the physical buttons on the device act very erratically. I don't have the well-known power button issue, but I have something similar. The power button doesn't work on a long-press. If you long-press the power button it should give you the power menu, right? In my case, that never happens. What will happen is the display will turn off, as if I simply pressed and released it, like when you lock the phone. No matter how long you hold it in, the power menu will never appear.
Other buttons also act odd. The volume down button does work, but it also triggers the multitasking window to appear, every time I press it. This behaviour is not restricted to being in Android. Scrolling in CWM with the volume rocker, because that is the only way you can navigate this version of CWM, also does this. The log window will disappear and re-appear constantly, but sometimes it doesn't do this. This problem is only with the volume down button. The volume up button works just like it should. Other buttons do give problems, but they are not ever-persistent like the ones I mentioned above. The others just have constantly changing behaviour. They will perform different tasks at random when pressed, like open the dialer, or go home, or open the multitasking window as well, or even go back sometimes.
Now, I don't know what happened to Tytung on XDA, nor do I want to find out because it isn't important to me, but I'm not trying to advertise his work. I'm just trying every ROM I can find.
The phone does have water damage, but that was many years ago. No repairs were done to it, but it still works just like it should. The only problems are the ones I mentioned above. I do think that the water damage did do something to the buttons of the phone, but is it even possible that Deep Sleep can be affected by this? Isn't Deep Sleep something that is software-based?
I really would like to know what the is going on here
Any help would be greatly appreciated
I hope I provided enough information about this problem
Click to expand...
Click to collapse
I have a similar set up with the opposite problem: won't come out of deep sleep! Hate to hijack your topic but if anyone knows what could be causing this...?
Related
I have a case on my phone that makes using the hardware buttons a real pain. Has anyone found, or does anyone know of any custom kernels or roms released that allow a 'sweep glass to wake' feature? I'm using widgetlocker now which allows a wake by pressing the volume buttons - which are easier than the power key, but if anyone has any suggestions (other than removing the case), I'm all ears.
I'm running the unNamed 2.1.1 rom w/entropy's kernel btw.
Thanks!
Matt
Don't know of any. Don't think anyone would even want one, besides you. I leave my phone in my pocket and it would constantly turn on when walking, if it was just a swype gesture. IMO, it would be a massive pain.
I'm 99% certain there is no way to do this without increasing battery drain significantly. Having the touchscreen controller active while in sleep would increase drain a lot, and also it's about 50% likely the touchscreen controller is not even capable of waking the CPU from deep sleep.
It would require a MASSIVE amount of kernel hacking to make it possible, and the battery drain would be awful.
Check out "Tap Tap App" in the market. I've been using it. It's a little strange as it doesn't always work. It does most of the time. I don't know what it does to the battery. I haven't checked it yet.
You're closest bet would be to find something that allows the capacitive keys to wake the screen (I believe some HTC devices can do that, as can my gTablet).
It might be as simple as editing a keymap file.
I recently got a strange touchscreen issue.
When the device comes out of deep sleep (turn on the screen with power button) my touchscreen behaves weird. Normally, when I touch the unlock slider, it follows my finger. But not now....it's like long press is not recognized. I am able to unlock the screen by wiping my finger to unlock. But the slider is not following my finger. The strange thing is, after about 10 seconds, the issue is gone, and the slider follows my finger....
Also long press on the homescreen is not working during the first 10 seconds.
What I tried to solve:
I completely wiped the phone and reinstalled .42 firmware. Then updated tot ICS using Sony Update Service and also completely wiped my phone. The problem still there...then I flashed a custom ROM (shardur_seth spacious...and also his firmware) but the problem stille there.
Anyone else experienced this? Or any solutions I could try? It was there suddenly....could it be a hardware problem? But why is it gone after 10 seconds?
Thnx for your help
it happens for me sometimes, but most of the time when someone calling me i cannot at slide to answer. what im doing is i just press power button ones and it will silence and press the home key and it will work the slide key...
any solution for this also?
mavado said:
I recently got a strange touchscreen issue.
When the device comes out of deep sleep (turn on the screen with power button) my touchscreen behaves weird. Normally, when I touch the unlock slider, it follows my finger. But not now....it's like long press is not recognized. I am able to unlock the screen by wiping my finger to unlock. But the slider is not following my finger. The strange thing is, after about 10 seconds, the issue is gone, and the slider follows my finger....
Also long press on the homescreen is not working during the first 10 seconds.
What I tried to solve:
I completely wiped the phone and reinstalled .42 firmware. Then updated tot ICS using Sony Update Service and also completely wiped my phone. The problem still there...then I flashed a custom ROM (shardur_seth spacious...and also his firmware) but the problem stille there.
Anyone else experienced this? Or any solutions I could try? It was there suddenly....could it be a hardware problem? But why is it gone after 10 seconds?
Thnx for your help
Click to expand...
Click to collapse
i face the same problem
my phone is in service center for repair
see the video below and check if ur problem is the same
Sounds like your phone is just sluggish, you're probably running too much in the background/have too much installed on the phone and it takes a while for the RAM to optimally load everything you need again after having cleared some of it whilst the phone was in sleep mode.
SCHUMI_4EVER said:
Sounds like your phone is just sluggish, you're probably running too much in the background/have too much installed on the phone and it takes a while for the RAM to optimally load everything you need again after having cleared some of it whilst the phone was in sleep mode.
Click to expand...
Click to collapse
i repaired my phone via SEUS but the problem usa still there
went to service centre ,they downgraded it to Gb the problem was still there!!!!
dhwanik said:
i face the same problem
my phone is in service center for repair
see the video below and check if ur problem is the same
Click to expand...
Click to collapse
Yes, that's exactly the problem.....I also have the problem that I cannot longpress the home screen...U have the same issue? After 10 seconds or after tapping the screen multiple times, the issue is gone until the phone goes to sleep.
I too had this issue and narrowed it down to the sluggishness due to deep sleep.
What I did was,
1) Flash nightelf kernel
2) Installed Set CPU
3) Make profiles for Screen Off
4) Whenever I have the governor as "performance" I never had the issue
5) After lot of permutation combination, I fixed a screen off profile as 460max and 134 Min with conservative as governor.
6) Also added a new profile for "In Call" with "performance" governor.
The problem was gone. Yes, it happens once in a while but much better than the situation before.
mavado said:
Yes, that's exactly the problem.....I also have the problem that I cannot longpress the home screen...U have the same issue? After 10 seconds or after tapping the screen multiple times, the issue is gone until the phone goes to sleep.
Click to expand...
Click to collapse
yes i have the same issue we are not the only users who face this problem
there are many users who face this problem
arunsankar said:
I too had this issue and narrowed it down to the sluggishness due to deep sleep.
What I did was,
1) Flash nightelf kernel
2) Installed Set CPU
3) Make profiles for Screen Off
4) Whenever I have the governor as "performance" I never had the issue
5) After lot of permutation combination, I fixed a screen off profile as 460max and 134 Min with conservative as governor.
6) Also added a new profile for "In Call" with "performance" governor.
The problem was gone. Yes, it happens once in a while but much better than the situation before.
Click to expand...
Click to collapse
i am on locked boot-loader so can't flash kernel
arunsankar said:
I too had this issue and narrowed it down to the sluggishness due to deep sleep.
What I did was,
1) Flash nightelf kernel
2) Installed Set CPU
3) Make profiles for Screen Off
4) Whenever I have the governor as "performance" I never had the issue
5) After lot of permutation combination, I fixed a screen off profile as 460max and 134 Min with conservative as governor.
6) Also added a new profile for "In Call" with "performance" governor.
The problem was gone. Yes, it happens once in a while but much better than the situation before.
Click to expand...
Click to collapse
Tried using your settings..first I had governor set to performance...but the problem still persists. Wheneven I turn on the screen I have the issue. It is possible to unlock the screen if I wipe fast enough....but it really is strange...why is the issue gone after a couple of wipes or some touchscreen pressess..
Could it be a hardware error....a sensor not getting ready or something? But why is the problem gone when the screen is on for a while.....
mavado said:
Tried using your settings..first I had governor set to performance...but the problem still persists. Wheneven I turn on the screen I have the issue. It is possible to unlock the screen if I wipe fast enough....but it really is strange...why is the issue gone after a couple of wipes or some touchscreen pressess..
Could it be a hardware error....a sensor not getting ready or something? But why is the problem gone when the screen is on for a while.....
Click to expand...
Click to collapse
I have the same problem. Is there any solution?
Thank you for help.
same problem
Feri8850 said:
I have the same problem. Is there any solution?
Thank you for help.
Click to expand...
Click to collapse
me also having same problem and touch is awesome but when the lock is open then this problem will occur and it will open after 2 to 3 attempts..
what's this i think this is not an hardware problem this is only the software ??//??
i have the same problem too. i think there is a problem with cpu.
I had these sometimes with certain combinations of kernel and ROM. Actually it's gone... (Alliance V1/JJs Hybrid ROM 3.1)
I suppose it's a combination of hardware and software configuration...
Anyone tried to higher the minimum CPU speed?
Nachttier73 said:
I had these sometimes with certain combinations of kernel and ROM. Actually it's gone... (Alliance V1/JJs Hybrid ROM 3.1)
I suppose it's a combination of hardware and software configuration...
Anyone tried to higher the minimum CPU speed?
Click to expand...
Click to collapse
i tried. also i tried to set governor to different versions. and i tried nightelf rc5 kernel. nothing changed. problem still there.
today i realized that's not about only touchscreen. sometimes phone freezing.
problem with neo (mt15i) touch screen
use alliance night-elf v1.1 kernel.I had this problem but when I flash this kernel to my neo my touch screen works good same as the first day...
Well....for me suddenly the problem is solved!!!!
I'm very glad that my display is working again! It has been for about 3 months since I was facing the problem.
Unfortunately I do not have a clear solution to this, but I can explain what I did that day, and hopefully the solution is in there. But I can not garantee it.
What I did that day
1. I tried to get beats audio working, so I had installed a numerous of Beats libs. (see xda-developers for some of those libs). The last one I tried was Walkman port by ThilinaC. Not sure how this can be related to the display issue
2. I flashed a new rom. But this time I formatted /system and /data in CWM. Normally I just did a factory reset and installed the new rom. (but guess factory reset also formats /system and /data)
Still....guess this has nothing to do with the display
3. I did a offline charge. When my phone was empty I wanted to charge it fast. So I switched off my phone, and then connected the charger to offline charge the phone.
Really not sure how the above points could be a solution to de display failure, but guess if it was the digitizer that was the problem, it's strange that it is fixed out of knowhere....but the above actions are what I did that day....so maybe it's helpful and is the solution in there...maybe.
I'm glad the problem is gone
Yes, I am facing this exact problem, I am going to take my mobile to the service center !!!.
Hi, yesterday I upgraded from Paranoidandroid 3.68 to the new project Paranoidandroid 3.99 from http://forum.xda-developers.com/showthread.php?t=2397762
But I have an annoying problem - The touch button backlight keeps randomly turning on and switches off only when i click on screen. This only happens when I use it, it seems to be some kind of response or something. I have gone in settings>buttons>backlight and disabled it yet this does not disable the random turning on of it. Anyone know how can I completely disable it without installing custom kernels? Or what is causing it to randomly turn on all the time.
That's due to the touch key backlights. On 4.2.2 (PA 3.68) there was an option to disable them. On 4.3 it was removed by CM so a lot of other ROMs don't have the option either. What I've done on other 4.3 ROMs is to install the device settings apk and use that to turn them off. I haven't tried it on PA though.
I'm on mobile so can't give you a link... Search through my past posts from a couple weeks back. I posted the apk and instructions a couple of times, once in the PACman thread, once in Q&A. I also saw the steps quoted in Q&A by someone else too, you might come across that thread.
Oh wait you could probably even go to my 'most thanked posts'. It might be one of those. See how you go.
Sent from a galaxy far, far away
Hmm, thanks! But I did that, installed whole custom settings apk and launched the custom settings and turned the backlight off in there too, but it's exactly the same. Also this rom already has backlight button setting in options, so it didn't do anything new as far as i can tell.
The key backlight turns on randomly after like 5-30sec of pressing on screen. It's not like the usual backlight turning on keypress but it turns on after some time instead.
Edit: Backlight keeps turning on even if i have the default 3sec deley. the backlight would turn off after 3 sec and then back on after like 10sec until screen turns off or i press again on screen. Weird, maybe rom bug? I cant post on rom thread because i don't have enough posts
Edit 2: OK I have linked it to screen brightness. Every time screen brightness changes (from adaptive lightning, screen timeout and app/game setting) the key backlight turns on. I have no idea how to force the key backlight to stay off though, so thats why im here
Oh wow. Good job narrowing it down to that, I imagine it wasn't easy to figure out what was causing it. Have you read the rom thread for the last 15 pages or so? See if someone else is having the same issue. Also read the OP and following posts, for known bugs /FAQ. You should have read OP before flashing anyway but read it again
If you don't find anything else, try to get a few extra posts and then post in the thread. You seem to know what you're doing, so try helping out a few other people on Q&A maybe.
Sent from a galaxy far, far away
The latest(todays) build fixed the issue. Thanks for help!
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
srdempster said:
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
Click to expand...
Click to collapse
My test device - that I picked up very cheep as it had been dropped and the SIM reader no longer works - displays the same issue, I had always assumed it was because of the fall it had.
Sorry if that doesn't help you
like this?
http://youtu.be/oyv5QmD5uQA
Exactly the same issue thanks
Same here but my phone is allways in case and i never dropped it. Oh and factory reset or flashing another ROM is not solution.
Any ideas?
I can only guess that either the RAM fills up with the screen off and once it starts to clear when the power button is pressed it suddenly can draw faster, or it's because the CPU and GPU clock down and slowly ramp up on wake. I'll change my performance settings see if that changes things?!
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
srdempster said:
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
Click to expand...
Click to collapse
So it's actually software problem right? Not damaged screen or something inside the phone.
Jecmenn said:
So it's actually software problem right? Not damaged screen or something inside the phone.
Click to expand...
Click to collapse
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
srdempster said:
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
Click to expand...
Click to collapse
mine is a hardware issue. you will see that it is currently on cm12 but it has done that on Stock, 4.4.x custom and 5.0 CM/AOSP as well. It will only do this if it hasn't be used for a few hours.
I notice that the double click of the power button still opens the camera in nougat and now there doesn't seem to be a way to switch it off. I've accidentally triggered this twice, hit home to close camera, then pressed the power button to switch off. Soon after on both occasions the phone has partially rebooted in my pocket, sticking on the Wiley fox boot logo.
Anybody else confirm this behaviour? Not something you do everyday I guess......
Hi Ratbags, I tried it for you... I never noticed that tapping the power button twice starts the camera, but indeed it does; however my phone didn't reboot (so it also didn't get stuck).
Hallo ratbags, i can confirm this behaviour in my Swift 2 Plus with Nougat Android. Noticed that randoms reboots some while ago and with your hint about power double click i am able to reproduce it.
To switch it off
Go to parameters
Use the search option and search gestures
Click on Gestures and then you'll find the option you are looking for
naegi said:
To switch it off
Go to parameters
Use the search option and search gestures
Click on Gestures and then you'll find the option you are looking for
Click to expand...
Click to collapse
Thanks for that. I believe Wiley fox are bringing out an update to fix this issue. Strange you can only get to that setting by searching or is it hidden away somewhere deep in a settings submenu?
ratbags said:
Thanks for that. I believe Wiley fox are bringing out an update to fix this issue. Strange you can only get to that setting by searching or is it hidden away somewhere deep in a settings submenu?
Click to expand...
Click to collapse
I didn't find it anywhere else so I think it's hidden
There's others hidden menu (and some are not even working at all - like battery percentage). I think that it's the trace of some modifications of parameters that weren't done correctly, or those parameters were disabled because the option didn't work well.
With latest update Build no. TOS118C the Gestures are available in Options Menu. The "not quite random reboot" seems to befixed too. Tested it several times and got no reboot since 3 hours.
Was just scanning the forum for any reports of random reboots as I've also been having reboots and it hanging on the white WileyFox logo screen.
Have noticed it more since the more recent official updates and have even gone so far as a full factory reset, however, I've had the issue reoccur several times since then (reset done earlier in week) so will be interesting to see if disabling that camera gesture will help
Beyond that I'm thinking possibly a corrupt or "worn" SD Card as I have a MicroSD card, used to extend the internal storage, that I think I used for a year or so in my previously Swift so possibly suffering some mild wear....