Related
I bit the bullet and installed Cyanogen Mod Version 7 3.5 and the market. After one reboot back into Android and one into WebOs I ran into the Cyanogen Mod boot loop. Searched quite awhile on how to get out of this and found I had to do a hard reset by pressing and holding the power and home buttons. After I did this I booted into Android with no problem. But now when in Android the screen shuts off and soon after reboots. Anyone one know what might have caused this? How to fix this?
Edit: Did a couple of reboots with no problem. Turned off the Zen Live Wallpaper and that seemed to fix the reboot when the screen turns off. We shall see.
BigBadWolf84 said:
I bit the bullet and installed Cyanogen Mod Version 7 3.5 and the market. After one reboot back into Android and one into WebOs I ran into the Cyanogen Mod boot loop. Searched quite awhile on how to get out of this and found I had to do a hard reset by pressing and holding the power and home buttons. After I did this I booted into Android with no problem. But now when in Android the screen shuts off and soon after reboots. Anyone one know what might have caused this? How to fix this?
Edit: Did a couple of reboots with no problem. Turned off the Zen Live Wallpaper and that seemed to fix the reboot when the screen turns off. We shall see.
Click to expand...
Click to collapse
You may want to use SetCPU and set the min freq to 594mhz at least to prevent this reboot. The higher the less likely to reboot but may cause battery drain. Mine is set to max 1404 mhz / min 594 mhz / on-demand.
Link to SetCPU : http://forum.xda-developers.com/showthread.php?t=505419 free donate version but i bought it anyway to support this app.
anyway this is the wrong section but ...
Moved to general.
Sent from my NexusHD2 using xda premium
am i the only one who experienced too much wake up delay?. i mean it took about 10-15 sec to wake it up. normally, when we press the home key, it'll wake up our ace within 1-2 secs, but in me it took 10 - 15 sec and i need to press the volume just to wake up my ace. i tried to reflash with odin, change my rom into cm 9, but no luck. what can i do to solve this problem?
Does it happens always? If so try setting min. frequency at 245 Mhz... Also governor to smartass v2
Prashanthme said:
Does it happens always? If so try setting min. frequency at 245 Mhz... Also governor to smartass v2
Click to expand...
Click to collapse
yes. it happens every time the screen turn off. i already did that, but nothing changed. i dont know what the problem of m ace
can someone tell me how to fix it?. it's really annoying. i always use my ace to check time, or check if there is any email, message received. but it always took about 10 - 15 secs to wake it up. dunno how did this happen to my ace. all i remember is i removed the sd card, then boom. it start to happen. and it always happen.
what is your internal memory free space and the RAM usage?
I also get the laggy problem when my dolphin browser is opened.
try RAM manager from pstore.
dianpadi said:
what is your internal memory free space and the RAM usage?
I also get the laggy problem when my dolphin browser is opened.
try RAM manager from pstore.
Click to expand...
Click to collapse
i have 83mb free in internal memory. dunno what is my RAM usage.. BUT, even if it is newly reflashed from odin, it still happens too much delay in wake up. so i try to flash a custom rom, CM 9 by mclaw, wipe the cache, wipe the delvik, restore factory settings, i already did all of them. but still, the the delay is there. 10-15 seconds delay in wake up..
how can i fix this?
I don't have this phone but i know it's related to the kernel
Sent from my LG-P500 using xda premium
FPChaim said:
I don't have this phone but i know it's related to the kernel
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
i'll try to flash a new kernel.
EDIT: already tried to flash a new kernel. still no luck..
what rom are you using? cm variants have a known issue of having delayed wake up lags, and if you alread had tried flashing over odin try flashing over customized stock rom which are aboundantly found in the development section
maybe your phone using default min. frequency, if yes, change to 245 MHz
but in my case, my min-max freq is default, and it didn't affect my phone's wake up time
My screen off profile in SetCPU is 120Mhz Min and 320 at Max. I never had wake up problems in my phone. My question is, 15 seconds waiting is looong. Do you press just middle (HOME) button and wait for 15 seconds? Because in either case if you were/are on stock ROM flashed via ODIN. That must not be happening on stock.
If you're using CM based ROM, Is everything check in "buttons" section in Settings > CyanogenMod Settings > Input Settings?
I'm just checking which buttons you've assigned to wake up your device.
mawnstermew said:
what rom are you using? cm variants have a known issue of having delayed wake up lags, and if you alread had tried flashing over odin try flashing over customized stock rom which are aboundantly found in the development section
Click to expand...
Click to collapse
i already tried stock rom from odin, still it has the wake up extreme lag that took 10-15 secs. then i tried to flash custom rom, cm9, cm 7.1, 7.2, stock based rom, still no luck.. i think, it's the hardware of my ace that has problem.
Rushyang said:
My screen off profile in SetCPU is 120Mhz Min and 320 at Max. I never had wake up problems in my phone. My question is, 15 seconds waiting is looong. Do you press just middle (HOME) button and wait for 15 seconds? Because in either case if you were/are on stock ROM flashed via ODIN. That must not be happening on stock.
If you're using CM based ROM, Is everything check in "buttons" section in Settings > CyanogenMod Settings > Input Settings?
I'm just checking which buttons you've assigned to wake up your device.
Click to expand...
Click to collapse
i dont set any buttons to wake up my ace, means, it was using the default. even in stock rom flashed via odin, it still have the extreme lag wake up. i press the home button, the light turn on in the menu and back button (left and right of the home button), and if i just wait, it wont turn the lights on in the screen, sometimes, if i just wait the 15secs, it'll wake up and imediately sleep again bout less than 1 second. that's why i need to press the volume to wake it up
can someone know how to fix it?
Try to set Minimum Clock Frequency to 245 or flash Adrenaline Boost v2 then if you feel that you are running low on memory just give your Ace a Boost.
Sounds weird, but you mentioned earlier that you removed your SD card without unmounting? Try formatting the card and insert it when the phone is off OR erase it when in CWM recovery. Never know this might just work out. If it doesn't use Kies to update your phone to stock.(Tedious process I know). Hope it helps.
I'm surprised nobody thought of this as a hardware problem.
Do you still have a warranty?
consegregate said:
I'm surprised nobody thought of this as a hardware problem.
Do you still have a warranty?
Click to expand...
Click to collapse
my warranty is already void/expired. i really think that this is a hardware problem. because, i already tried what they said.. but nothing happens. still the same. i already tried to reflash again via odin twice. still got the extreme wake up delay. tried to flash a custom rom based on stock, still no luck, tried to flash a cm rom (7.1, 7.2, 9) still the same. tried to set the minimum frequency to 245, still the same. and i think, im the only one experiencing the 15 second wake up delay. that's why i think, it's the hardware that has the problem.
Xr01d_GT said:
Sounds weird, but you mentioned earlier that you removed your SD card without unmounting? Try formatting the card and insert it when the phone is off OR erase it when in CWM recovery. Never know this might just work out. If it doesn't use Kies to update your phone to stock.(Tedious process I know). Hope it helps.
Click to expand...
Click to collapse
i already did that. i think, it's not on SD. because it still happen with or without sd on my ace.
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 !!!.
When I set my clock settings to 'Automatic' the clock starts running to slow(?). after 8 hours the time is already 5 minutes behind.
I did a full wipe and installed again but still have the same issue. Anybody else who can help me?
update: It also happens when I use manual time settings. And the issue seems to be that the time 'jumps' backwards at some point. When I don't actually use the phone it happens to a lower degree ( ±1sec), when I use it it's more. Yesterday it was ±15sec, now it's already 30)
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...?