I'm having problems with my phone, when the screen turns off, it turns on again and I don't know what's happening... I previously changed timeout to 30 min because I was downloading stuff then I change it back to 30 s but now I have this issue. What should I do?
rolo143 said:
I'm having problems with my phone, when the screen turns off, it turns on again and I don't know what's happening... I previously changed timeout to 30 min because I was downloading stuff then I change it back to 30 s but now I have this issue. What should I do?
Click to expand...
Click to collapse
did you overclock your cpu and what rom/kernel are you using?
Raider_ said:
did you overclock your cpu and what rom/kernel are you using?
Click to expand...
Click to collapse
I have cyanogenmod 7.2 installed on my phone. The kernel is the one for this rom, i installed at the same time i installed this rom.
i dont know too much about overclocking but on cyanogenmod settings i selected "smartass". The default mode is "interactive" but i already tried switching between these and it doesn't solve the problem. the max overclock i think is at 1024. That's it
But the screen sometimes flashed and it's a little bit scary at times let me tell you because it is sleep and all of a sudden it turns on the screen, its like is possesed or something. xD
Can someone please help me? I thought the problem was solved but this issue is getting me out of my nerves, after the timeout screen goes off, the screen turns on again by itself for about 3 times. I don't know what to do, but it's draining battery because of this. Please help.
rolo143 said:
Can someone please help me? I thought the problem was solved but this issue is getting me out of my nerves, after the timeout screen goes off, the screen turns on again by itself for about 3 times. I don't know what to do, but it's draining battery because of this. Please help.
Click to expand...
Click to collapse
Try to set the governor to ondemand and the scheduler to sio or noop set it on boot, then reboot to cwm, clear dalvik cache and reboot system. If that doesnt work. Backup, reflash rom and kernel, then advance restore data only.
evilbarcode said:
Try to set the governor to ondemand and the scheduler to sio or noop set it on boot, then reboot to cwm, clear dalvik cache and reboot system. If that doesnt work. Backup, reflash rom and kernel, then advance restore data only.
Click to expand...
Click to collapse
Where can I change the scheduler option? I already tried wiping the dalvik cache and changing the governor to "ondemand" reboot, but the problem is still there, when the phone goes to sleep, it turns the screen on again about 5 or 6 times then it turns off and after a while it repeats.
evilbarcode said:
Try to set the governor to ondemand and the scheduler to sio or noop set it on boot, then reboot to cwm, clear dalvik cache and reboot system. If that doesnt work. Backup, reflash rom and kernel, then advance restore data only.
Click to expand...
Click to collapse
Raider_ said:
did you overclock your cpu and what rom/kernel are you using?
Click to expand...
Click to collapse
What has scheduler or governor or OC to do with this?
Sent from my Xperia Arc S using xda premium
The thing is I can't solve this problem, do you think if i reflash firmware and kernel it would be ok? But I dont want to lose my apps or data, and if I make a backup before reflashing then i restore it, would the problem come back? Please, I need to put an end to this thing, is driving me crazy!
EDIT: I attached a txt file with my logs. Using "aLogcat" app, I found this:
Maybe it can help..?
Does someone knows what is this about?
W/asset ( 346): deep redirect failure from 0x01030046 => 0x02080019, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x7f0d0008
if you see the logcat attached to my previous post, you see it repeats A LOT so I guess the problem is there but I don't know.... My screen is still turning on several times after going to sleep......I noticed a battery drain about 3% - 4% per hour so I don't think it's normal, when I go to sleep I have to have my phone on so the alarm sounds but for example I go sleep at 12:00 am and by the time i wake up 6:00 am in only 6 hours is about 15% or more drain..... I need to solve this problem
Related
hey everyone,
i have a strange issue and hope that someone can help me.
I use the neopeek Roms a lot and i have tried every single kernel.
But whenever the phone is in sleep mode io dont get any phone calls. the phone wakes up (red led) but thats it.
after i called my phone while it was in sleep mode it wouldnt go back into sleep mode.
i dont have this issue with the system.ext file androids.
over at neopeek.com we couldnt find a solution thats why im posting it over here.
thank you for ure help!
nick
the-nj said:
hey everyone,
i have a strange issue and hope that someone can help me.
I use the neopeek Roms a lot and i have tried every single kernel.
But whenever the phone is in sleep mode io dont get any phone calls. the phone wakes up (red led) but thats it.
after i called my phone while it was in sleep mode it wouldnt go back into sleep mode.
i dont have this issue with the system.ext file androids.
over at neopeek.com we couldnt find a solution thats why im posting it over here.
thank you for ure help!
nick
Click to expand...
Click to collapse
try pm.sleepmode=2 in your startup.txt
Eodun said:
try pm.sleepmode=2 in your startup.txt
Click to expand...
Click to collapse
We should not be using this in the newer kernels. BZO made a commit to the PLL2 code, and you should now either be using =1 or =0. I'd recommend =1 if you're OC'd, =0 if not. But not =2, assuming you're on a newer kernel (within the last 2 months I'd say...)
Also, to the OP - does this happen on FRX04 builds...? You also said you tried "every kernel" - there's some newer ones than autobuild, like 1253 - have you tried that?
hey,
thanks for your fast replies.
i already tried pm.sleep_mode 1 and 2 i have tried with and without oc.
currently im testing the FROYO B. but i have this issue with every build. ive tested every build so far. and i tried every other kernel i could find besides the autobuild. tested the 1253, the other one here at xda and the neopeek kernels.
had no luck with any kernel.
i had the same problem with the screen call ... it did not wake on any call but after i changed sleep mode to 2 it worked perfect
excuse my language
thank's man
hey,
thanks...i dunno why cuz normally pm.sleep_mode=2 shouldnt work but for some reason it does...seems to work...thanks
the-nj said:
hey,
thanks...i dunno why cuz normally pm.sleep_mode=2 shouldnt work but for some reason it does...seems to work...thanks
Click to expand...
Click to collapse
I tried sleep mode 1 and 2, still won't wake up. I also keep trying every new update between the kernel testing and the rootfs.
radcpuman said:
I tried sleep mode 1 and 2, still won't wake up. I also keep trying every new update between the kernel testing and the rootfs.
Click to expand...
Click to collapse
Are you overclocking? Assuming you're using a fairly new kernel, you should either be using 1 or 0 for the sleep_mode setting.
arrrghhh said:
Are you overclocking? Assuming you're using a fairly new kernel, you should either be using 1 or 0 for the sleep_mode setting.
Click to expand...
Click to collapse
No overclock. I have the latest test kernel and even today's rootfs update.
Here is my startup.txt.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot north_am_dialing=0 force_cdma=0 hw3d.force=0 physkeyboard=tilt2 pm.sleep_mode=0"
boot
I tried sleep_mode=1 earlier. If the LED is flash green, it doesn't wake up. I only started using the test kernels because non test stuff was doing the same thing. Everything else is working great since I turned off the GPS settings.
Would the incoming call issue be something that could be seen in log files by chance?
radcpuman said:
No overclock. I have the latest test kernel and even today's rootfs update.
Here is my startup.txt.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot north_am_dialing=0 force_cdma=0 hw3d.force=0 physkeyboard=tilt2 pm.sleep_mode=0"
boot
I tried sleep_mode=1 earlier. If the LED is flash green, it doesn't wake up. I only started using the test kernels because non test stuff was doing the same thing. Everything else is working great since I turned off the GPS settings.
Click to expand...
Click to collapse
There's some old deprecated commands in there. I highlighted them in red.
Also, why are you disabling hw3d? In addition, why do you have the north_am_dialing statement in there if it's set to 0? Also, I would definitely switch the sleep mode to 1.
What system image are you using? FRX04? I don't have this issue whatsoever, assuming the phone is doing OK (no SoD condition, no pegging proc, etc) the phone always wakes up for calls...
Have you tried deleting your data.img?
arrrghhh said:
There's some old deprecated commands in there. I highlighted them in red.
Also, why are you disabling hw3d? In addition, why do you have the north_am_dialing statement in there if it's set to 0? Also, I would definitely switch the sleep mode to 1.
What system image are you using? FRX04? I don't have this issue whatsoever, assuming the phone is doing OK (no SoD condition, no pegging proc, etc) the phone always wakes up for calls...
Have you tried deleting your data.img?
Click to expand...
Click to collapse
I'm using FRX04. Most of the setting except for pm.sleep_mode came from the startup utility. I have deleted the data.img once. I've even re-sized it to 769mb.
With the latest kernel image and rootfs I haven't had any issues except the dpad backlight stays on for a long time and incoming call issues. Then after a while will return to normal.
Should I take the hw3d out or set it to 1?
radcpuman said:
I'm using FRX04. Most of the setting except for pm.sleep_mode came from the startup utility. I have deleted the data.img once. I've even re-sized it to 769mb.
With the latest kernel image and rootfs I haven't had any issues except the dpad backlight stays on for a long time and incoming call issues. Then after a while will return to normal.
Should I take the hw3d out or set it to 1?
Click to expand...
Click to collapse
You can either take the hw3d statement out, or set it to one - they both should have the same effect.
There is no 'dpad' on the TP2. Do you mean the 4-button row at the bottom...? If those lights are on at boot, they will stay on in Android, so make sure they do not turn on at boot. Basically get the phone in portrait mode and wait until the button lights go dark.
Please try your data.img again. You can simply rename it, this is just a test - that file gets messed up and causes odd effects, this might be one of those instances.
arrrghhh;11295243
Please try your data.img again. You can simply rename it said:
Thanks for you help arrrghhh!
I renamed the data.img. Started it up, signed in to my google account to sync contacts. Waited for it to go to sleep, then called the phone. The LED went to amber, but didn't wake up and ring. I have the sleep_mode set to 1. I set the 3d setting to 1.
Click to expand...
Click to collapse
Hello to everybody!
Yesterday i came on with a big problem. I had connected to my brothers wifi.(he turned tethering on his huawei u8500) One moment, i have lost the connection with him.I tryed to reconnect to his network but nothing.Then i went outside my home and tryed to connect to my neighbours open wifi connection, but nothing.
All the time there shows - gathering ip address, and after about 20sec it says dissconnected, and it starts from beginning.
As for SetCpu all was fine, till yesterday again.My freq was 480/729 .
After the wifi problem,i restarted the phone in recovery, and cleaned cache and dalvik..and thought that it will fix the problem but nothing.I turned the phone on, all was o.k Then i opened setcpu as always when i turn on my o1 and wanted to change frequencies, but nothing happened. Superuser allowed setcpu, but nothing.
Through CM settings i can change the freq, but through setcpu - nothing.
After all, before about 1 hour i backed up this rom, and installed CM.6.5.8. All worked fine- setcpu and wifi.
My current rom is CM7 6.5.7
Kernel - franco.v19.-bfs
I don`t want to flash to another rom, becouse later it wil be hard to get all apps and all other things back.
I don`t have any idea what went wrong
Maybe someone can help me?
p.s sorry for my mistakes, if there are any.
Esterra said:
Hello to everybody!
Yesterday i came on with a big problem. I had connected to my brothers wifi.(he turned tethering on his huawei u8500) One moment, i have lost the connection with him.I tryed to reconnect to his network but nothing.Then i went outside my home and tryed to connect to my neighbours open wifi connection, but nothing.
All the time there shows - gathering ip address, and after about 20sec it says dissconnected, and it starts from beginning.
As for SetCpu all was fine, till yesterday again.My freq was 480/729 .
After the wifi problem,i restarted the phone in recovery, and cleaned cache and dalvik..and thought that it will fix the problem but nothing.I turned the phone on, all was o.k Then i opened setcpu as always when i turn on my o1 and wanted to change frequencies, but nothing happened. Superuser allowed setcpu, but nothing.
Through CM settings i can change the freq, but through setcpu - nothing.
After all, before about 1 hour i backed up this rom, and installed CM.6.5.8. All worked fine- setcpu and wifi.
My current rom is CM7 6.5.7
Kernel - franco.v19.-bfs
I don`t want to flash to another rom, becouse later it wil be hard to get all apps and all other things back.
I don`t have any idea what went wrong
Maybe someone can help me?
p.s sorry for my mistakes, if there are any.
Click to expand...
Click to collapse
Try the latest kernel CFS by fserve
The same,
It`s not working with that kernel.
i also tryed Goldenleaf versions, and i had francis franco v18 kernel.It is not working too...
What could be the problem?
Hello
I recently flashed XXLA2 and Speedmod 19 test 5. Now my phone is randomly restarting (so far 3 times in the 28 hours since flashing it).
Also, sometimes when I turn my phone on the 4 home buttons have changed to random apps, and each of my home screens are blank.
Does anyone have any thoughts about what is causing this or what I could do to fix it?
Thank you! (And ill give thanks for any good answer!)
It's an alpha build so you should expect everything will be working smooth and properly.
jbarol said:
Hello
I recently flashed XXLA2 and Speedmod 19 test 5. Now my phone is randomly restarting (so far 3 times in the 28 hours since flashing it).
Also, sometimes when I turn my phone on the 4 home buttons have changed to random apps, and each of my home screens are blank.
Does anyone have any thoughts about what is causing this or what I could do to fix it?
Thank you! (And ill give thanks for any good answer!)
Click to expand...
Click to collapse
Try doing a Wipe cahe and wipe dalvik cache and check it you still getting reboots.
While installing a New Base/ROM, its always preferable to do a full wipe before installation.
Hope this helps!
ksantoshh said:
Try doing a Wipe cahe and wipe dalvik cache and check it you still getting reboots.
While installing a New Base/ROM, its always preferable to do a full wipe before installation.
Hope this helps!
Click to expand...
Click to collapse
wiped this morning, so far no reboots. ill let you know if that changes.
thanks!
This morning I had another freeze then reboot. The phone was on power saving, and i was swiping between screens when it happened. once it turned on again, it showed the blank screens with the incorrect home buttons.
Happy holi guys
I flashed my rom regularly with 6 times a day
I am preparing script and tweak for battery + performance + tweak who itself adjust a cpu when doing CPU kinda work
Now problem arises below
i havent seen any degradation as once i have seen battery sucked. now i am sufering with serious problem one time i overclocked and its a time my cpu stucked at 902 mhz when i set to 806 mhz my device reboots itself and itself came to 902 battery is also good guys please help me if u can i want back to 800 mhz
Performance is also good no random reboots and none other problem. Why my cpu stucked at 902 mhz default
Help appriciated
the software which you used to overclock like setcpu is doing that setting at boot as you might checked set on boot option...
best option is connect to pc , go to recovery and uninstall setcpu or if you have created the recovery zip from setcpu you can use that too
madman_amit said:
the software which you used to overclock like setcpu is doing that setting at boot as you might checked set on boot option...
best option is connect to pc , go to recovery and uninstall setcpu or if you have created the recovery zip from setcpu you can use that too
Click to expand...
Click to collapse
Happy holi guys i tried this but my damn cpu stucked 902 whenever i changed my setting it itself came back to 902 mhz
Happy holi to you too
I have no idea about your problem but uninstalling setcpu might help or just flash a new kernel
A noob here
------------
May The Force Be With You
Well ... Might be the Script problem ... re-flash a new Script ... or reflash a new rom
that would solve ur problem ...
jumbobombo said:
Happy holi to you too
I have no idea about your problem but uninstalling setcpu might help or just flash a new kernel
A noob here
------------
May The Force Be With You
Click to expand...
Click to collapse
Yea the kernel reflash might workk
Sent from my GT-S5830 using xda premium
hii
sorry about my english i try to explain shortly
Phone in deep sleep, wont ring at all, it wont even show a missed call
If I wake the phone up and call it, phone rings almost instantly.
.Full wipe and re-install of ROM and I am getting the same crap.
I am completely back to stock, factory reset and all. The issue is still happening, if the screen is off and phone is in sleep the device will not ring
i also odin'd the modems,kernels and same.
i dont have warrenty, there is something i can do?
help me plz!:crying:
yairalm said:
hii
sorry about my english i try to explain shortly
Phone in deep sleep, wont ring at all, it wont even show a missed call
If I wake the phone up and call it, phone rings almost instantly.
.Full wipe and re-install of ROM and I am getting the same crap.
I am completely back to stock, factory reset and all. The issue is still happening, if the screen is off and phone is in sleep the device will not ring
i also odin'd the modems,kernels and same.
i dont have warrenty, there is something i can do?
help me plz!:crying:
Click to expand...
Click to collapse
Hmm ... should be modem-related.
Try to flash another modem (for your region + mobile carrier).
Then wipe cache and Dalvik cache and fix permissions if you have CWM.
Have you changed the development settings?
Or energy saving?
Or have you a task killer app installed?
Good luck !
It_ler said:
Hmm ... should be modem-related.
Try to flash another modem (for your region + mobile carrier).
Then wipe cache and Dalvik cache and fix permissions if you have CWM.
Have you changed the development settings?
Or energy saving?
Or have you a task killer app installed?
Good luck !
Click to expand...
Click to collapse
i flash 4 kind of modems the last is my carrier modem(ki2)
now i on stock (lpd) with no app insttalled and i didnt tauch development setting.
you have more idea?