Hi
sry that i have created a new thread here, but i cant reply in the right thread in the development forum as a new member -.-
I have problems with Sip clients receiving calls when screen is off. This was with your 1.4 kernel.
With Francos 11.11 test kernel I can receive SIP calls with display off, but I doubt deep idle is up and running with his.
Edit: Was only the camera bug with francos build. Now Deep idle kicks in and i can receive SIP calls.
MIUI 1.11.4 (ht*p://miui-ger***.de Version)
xRising_Sunx said:
Hi
sry that i have created a new thread here, but i cant reply in the right thread in the development forum as a new member -.-
I have problems with Sip clients receiving calls when screen is off. This was with your 1.4 kernel.
With Francos 11.11 test kernel I can receive SIP calls with display off, but I doubt deep idle is up and running with his.
Edit: Was only the camera bug with francos build. Now Deep idle kicks in and i can receive SIP calls.
MIUI 1.11.4 (ht*p://miui-ger***.de Version)
Click to expand...
Click to collapse
Hmm. No idea what Franco has put in his 11.11 test kernel; did you check idle_stats that DEEP IDLE is actually working in his kernel? Does it work with GLaDOS if you disable DEEP IDLE? Did you try the BFS or CFS version? Are you using the mobile data connection or WiFi for the SIP calls?
Ezekeel said:
Hmm. No idea what Franco has put in his 11.11 test kernel; did you check idle_stats that DEEP IDLE is actually working in his kernel? Does it work with GLaDOS if you disable DEEP IDLE? Did you try the BFS or CFS version? Are you using the mobile data connection or WiFi for the SIP calls?
Click to expand...
Click to collapse
thx for answering.
I always use the cfs version. Bfs was unreliable, crashing and other small errors.
I am using Wifi for the SIP clients. Tested with 3cxphone,Sipdroid and Csipsimple but NOT with the built in client. The built in client is useless anyway.
Francos kernel IS running with Deep idle. The Deep Idle TOP ON and TOP OFF stats are counting correctly according to my BT setting.
Later today or tomorrow I will try disabling Deep Idle in your kernel and your test build.
I think problem is in init.d folder, maybe unusual scripts from another kernels blocking phone going to deel pidle.. On my i9023 is GlAdOs only kernel with working Deep Idle
xRising_Sunx said:
thx for answering.
I always use the cfs version. Bfs was unreliable, crashing and other small errors.
I am using Wifi for the SIP clients. Tested with 3cxphone,Sipdroid and Csipsimple but NOT with the built in client. The built in client is useless anyway.
Francos kernel IS running with Deep idle. The Deep Idle TOP ON and TOP OFF stats are counting correctly according to my BT setting.
Later today or tomorrow I will try disabling Deep Idle in your kernel and your test build.
Click to expand...
Click to collapse
Try the latest update GLaDOS V1.5. I have improved the stability of the wireless connection; maybe that did do the trick.
Ezekeel said:
Try the latest update GLaDOS V1.5. I have improved the stability of the wireless connection; maybe that did do the trick.
Click to expand...
Click to collapse
Your new kernel solved the bug. Thank you very much.
notabene said:
I think problem is in init.d folder, maybe unusual scripts from another kernels blocking phone going to deel pidle.. On my i9023 is GlAdOs only kernel with working Deep Idle
Click to expand...
Click to collapse
I clear my init.d folder, dalvik and cache when updating kernels. ^^
Related
Hi Everyone,
This is a recompiled version of Hastarin’s HD2 Android kernel that can be applied to most HTC HD2 RAM Android builds including DarkStone’s SuperRAM 1.5 build. The additional benefits over most existing builds is the inclusion of CIFS, or the ability to use CIFSManager to mount and unmount shared folders on your local network.
Download, installation instructions, and FAQ
If anyone needs any other version, non-oldcam, etc, just let me know and I'll add it to the downloads.
Thanks,
B.
will try this asap
Nice, cifs is very useful for me.
Thank you for compiling.
I should also point this out just in case, though I don't think it had anything to do with a kernel switch, as I was changing a million different things as I built the kernel. When I started using SuperRAM 1.5, my HD2 idled at about 7MA. Once I updated the kernel, and did a million other things, I was idling at about 60MA. After resetting back to the original data.img from SuperRAM 1.5, it dropped back to 7MA. All of this was using the same, attached, kernel.
So, as stated, it's obviously not anything to do with the active kernel, but in case anyone else has the problem, I would recommend going back to the original data.img and re-setting up.
Thanks,
B.
this work for Cedesmith new Initrd?
Thanks heaps ^_^
Sent from my HTC Desire using XDA App
Thanks! I do have something to ask, though - could cifs be compiled as a module so we could load it externally via insmod?
I don't know whether this is related to kernel or not.
I love the latest RAM builds, but with all these builds, my SE Bluetooth stereo headset hard buttons aren't working. Can u fix this issue.
Because of this small issue I cannot use these builds. Thanks in advance
Sent from my HTC DesireHD2 using XDA app
Good job !
This is useful for me, and how about "nls_utf8.ko" module?
We need utf8 for CIFS manager.
Is this build the same as darkstone superram
Sent from my HTC Desire using XDA App
Fmstrat said:
I should also point this out just in case, though I don't think it had anything to do with a kernel switch, as I was changing a million different things as I built the kernel. When I started using SuperRAM 1.5, my HD2 idled at about 7MA. Once I updated the kernel, and did a million other things, I was idling at about 60MA. After resetting back to the original data.img from SuperRAM 1.5, it dropped back to 7MA. All of this was using the same, attached, kernel.
So, as stated, it's obviously not anything to do with the active kernel, but in case anyone else has the problem, I would recommend going back to the original data.img and re-setting up.
Thanks,
B.
Click to expand...
Click to collapse
I have been testing SuperRam 1.5 with current kernel patch from original thread last couple of days, and I have been monitoring current usage since yesterday evening with different options. From what I have seen so far it will stay 6/7/8amp for some time and if you use the HD2 (browser/maps) for few minutes and put it in standby again, it might go back to 60amp. I reproduced this several times.
The most reliable I got was when I disabled mobile data, auto sync, GPS, BT, Wifi, but 3g is on. it consistently gives 7amp so far.
Current widget is set to log every 180sec.(if you set lower this widget might itself will interfere with readings as it has to write to SD card)
I think there is a bug in sync or mobile data which is causing this, it can't be just any change in data.img.
windroidHD said:
I have been testing SuperRam 1.5 with current kernel patch from original thread last couple of days, and I have been monitoring current usage since yesterday evening with different options. From what I have seen so far it will stay 6/7/8amp for some time and if you use the HD2 (browser/maps) for few minutes and put it in standby again, it might go back to 60amp. I reproduced this several times.
The most reliable I got was when I disabled mobile data, auto sync, GPS, BT, Wifi, but 3g is on. it consistently gives 7amp so far.
Current widget is set to log every 180sec.(if you set lower this widget might itself will interfere with readings as it has to write to SD card)
I think there is a bug in sync or mobile data which is causing this, it can't be just any change in data.img.
Click to expand...
Click to collapse
+1 to this. I have the exact same experience after days of testing. If I leave the phone alone in airplane mode with only wifi enabled, the phone lasts for like 5 days, and keeps 3-7mA idle readings. If I refresh the browser, it stays at 60mA for a while, but then eventually lowers back to 6/7mA after a while.
I'm also on Froyo RAM edition 1.5.
Is extended battery supported in this kernel?
windroidHD said:
I have been testing SuperRam 1.5 with current kernel patch from original thread last couple of days, and I have been monitoring current usage since yesterday evening with different options. From what I have seen so far it will stay 6/7/8amp for some time and if you use the HD2 (browser/maps) for few minutes and put it in standby again, it might go back to 60amp. I reproduced this several times.
The most reliable I got was when I disabled mobile data, auto sync, GPS, BT, Wifi, but 3g is on. it consistently gives 7amp so far.
Current widget is set to log every 180sec.(if you set lower this widget might itself will interfere with readings as it has to write to SD card)
I think there is a bug in sync or mobile data which is causing this, it can't be just any change in data.img.
Click to expand...
Click to collapse
In regular SuperRam (and other builds i think) I notice 60ma or 20ma standby drain after using the browser for a few minutes, especially if I was watching flash content, but it eventually settles down to 7ma. I have not added this kernel or tried it yet, I am just mentioning this because what you described there is what I see with my config normally.
will try this out! Thanks!
Can you also post the non-oldcam version? cifs supports works ver well.
Thanks!
pablo71 said:
In regular SuperRam (and other builds i think) I notice 60ma or 20ma standby drain after using the browser for a few minutes, especially if I was watching flash content, but it eventually settles down to 7ma. I have not added this kernel or tried it yet, I am just mentioning this because what you described there is what I see with my config normally.
Click to expand...
Click to collapse
Agreed, I noticed this running SuperRAM 1.5 prior to changing kernels as well.
Renegade_Rulez said:
Is extended battery supported in this kernel?
Click to expand...
Click to collapse
Yes. oldcam_eb stands for "Old camera library files with extended battery support."
Renegade_Rulez said:
Can you also post the non-oldcam version? cifs supports works ver well.
Thanks!
Click to expand...
Click to collapse
What build would this be for? Just want to make sure I include the right things.
Thanks,
B.
I'm using CF's rooted kernel and nothing else on my KLA4 Note. No other alternative kernels, just the stock one. And yet I keep seeing strange issues with the kernel. Is anyone getting any of these two?
1) gps causing a wakelock in betterbatterystats in kernel section
2) fuelgauge also causing a wakelock in betterybattery states in kernel section
It doesn't happen often, but it has happened out of the blue. And before you ask, no, GPS was never enabled, no apps I have in my phone are using GPS too. Happened over the weekend with no other activity on the phone other than some calls. A reboot fixed it.
As for the fuelgauge thing, I have no idea either. It happened after removing my phone from a charger, and noticed that the battery was draining fast. Sure enough looking at BBS, I see fuelgauge wakelocking in kernel, whatever that is. A reboot fixed it.
Anyone else facing these strange issues?
If it helps to know, I have it too. I seem to be able to trigger the GPS wakelock issue when the Browser attempts to fix my location but is somehow unable to. But not always.
Fuel gauge. Seems random, but it might be related to the battery being too stressed and the level "rising" a bit when relaxed.
I've tried the stock android kernel and now am CFRoot kernel with Checkrom v5. If anything the gps issue has increased.
I had a high Android OS usage with CF kernel and LA4. I switched to Abyss Kernel and the OS usage is next to none now. No wakelocks except those for sync. Phone has deep sleep now and the battery life is outstanding.
Blue1k said:
I had a high Android OS usage with CF kernel and LA4. I switched to Abyss Kernel and the OS usage is next to none now
Click to expand...
Click to collapse
I had the same with stock kernel. On low-use days my kernel was using 40% of the battery!
It finally forced me to flash a kernel, and I chose Abyss. Kernel is now less than 5% pretty much all the time. Deep sleep is also most of the time, although I did not check well before that.
My phone randomly reboots. This happened over a few weeks ago, I wiped cache and monitored it, it fixed it.
Today, it just rebooted.
I think its more a software problem rather than hardware.
Any suggestions.
P.S. Not to threadjack, but I am also on LA4 CF Root with CheckROM
There's a separate thread in the Q&A section about the GPS Wakelock problem.
http://forum.xda-developers.com/showthread.php?t=1419087
Some ideas to try and avoid it, but unfortunately nothing definitive yet.
Just as an aside, personally I've been using the 'wake up lag' characteristic of the exynos when coming out of Deep Sleep as a clue to these wakelocks. If the screen comes on immediately, I suspect a wakelock of some sort and check BetterBatteryStats and CPUSpy.
I found a bug about BLN.
My phone gets freeze when i have more than one missing calls. Somebody gave me two or more calls while i didn't notice my phone. When i noticed it, i can't switch on the phone but doing a battery pull.
It's not related to other mods such as BLD, TW, too low min cpu freq, live OC, deep idle and undervolted. Because i've switched all options on and off respectively under the same scenario when the problem occurred.
Finally i turned off the Blink Status (status can be switched on though), my phone can be able to have more than one missing calls without the problem.
My settings are as follows:
ROM: IMM26 4.0.4 port form ns4g by evilisto
Kernel: Air Kernel v3.4.5
Maybe some devs can solve the problem
kwokyu127 said:
I found a bug about BLN.
My phone gets freeze when i have more than one missing calls. Somebody gave me two or more calls while i didn't notice my phone. When i noticed it, i can't switch on the phone but doing a battery pull.
It's not related to other mods such as BLD, TW, too low min cpu freq, live OC, deep idle and undervolted. Because i've switched all options on and off respectively under the same scenario when the problem occurred.
Finally i turned off the Blink Status (status can be switched on though), my phone can be able to have more than one missing calls without the problem.
My settings are as follows:
ROM: IMM26 4.0.4 port form ns4g by evilisto
Kernel: Air Kernel v3.4.5
Maybe some devs can solve the problem
Click to expand...
Click to collapse
I can also confirm something similar like this. Also AirKernel v3.4.5, 4.0.4 PixelRom (even tho I think I had this on 4.0.3 roms, too). Buttons blink, but can't turn on my screen. Even music went till the end of song, didn't go to next song, and then I removed battery. No LiveOC nor OC, no DeepIdle...
Sent from my Nexus S using xda premium
Doesn't happen here:
Left 3 missed calls in my cellphone, buttons blink as they should, and phone wakes up as it should.
BLN Pro, but didn't happen in the free version either.
robrob777 said:
Doesn't happen here:
Left 3 missed calls in my cellphone, buttons blink as they should, and phone wakes up as it should.
BLN Pro, but didn't happen in the free version either.
Click to expand...
Click to collapse
What rom and kernel do you use?
kwokyu127 said:
What rom and kernel do you use?
Click to expand...
Click to collapse
This is my setup:
http://forum.xda-developers.com/showthread.php?p=22328954#post22328954"
This post should actually show up in the respective development thread, but I am not entitled to post there (http://forum.xda-developers.com/showthread.php?t=1700904).
I recognized that my I9000 did not enter deep sleep anymore after I had upgraded my kernel from 0.79 to 0.98.2. I tried all kinds of things, but nothing changed. When 0.98.3 came out, I upgraded to that, but still no deep sleep. BetterBatteryStats indicated that "suspend_backoff" was part of the problem. I re-flashed several times, froze many apps, and tried to track down the problem with no success.
I ended up going back to 0.79 and from that moment, deep sleep was working again. Consequently, I suppose that kernel version Devil3_0.98 might have a problem with deep sleep.
Did anybody here see similar problems with 0.98? This might be an example: http://forum.xda-developers.com/showpost.php?p=28280095&postcount=1330
(ROM: AOKP b40)
I just flashed 0.98.3 again, and now deep sleep works there also. This leaves me puzzled...
Quote:
Originally Posted by Kurre
Use BetterBatteryStats to investigate what app is keeping your phone awake. You'll find free XDA version from chamonix's thread here in XDA
Sent from my GT-I9000 using Tapatalk 2
done that, did not see anything useful.
heres a screenshot from now, if anyone can help out with this.
Thanks
ATTACHED THUMBNAILS
Click to expand...
Click to collapse
(cited from thread http://forum.xda-developers.com/showthread.php?p=28364531#post28364531)
Hi, I am pretty sure that you have the same issue that I have (I respond here because I am not allowed to post in dev forum). I bet BetterBatteryStats shows the kernel wakelock "suspend_backoff" as topmost entry, right?
I have new insights about this. I can reproduce the problem with kernels Devil3_0.98.3 and Devil3_0.79 (the only one I tried). So, it is not caused by the current kernel version. Steps to reproduce the no deep sleep problem:
flash kernel --> deep sleep works, but no deep idle
enable "Toggle Deep Idle" in Devil Kernel Config
reboot --> deep idle works but only with TOP=on, deep sleep still works
enable "Bluetooth kill" in "Devil Kernel Config"
save init.d file in "Devil Kernel Config"
reboot --> no more deep sleep, BetterBatteryStats shows kernel wakelock "suspend_backoff", deep idle works with TOP=off
So, this seems to be kernel related, and Bluetooth kill seems to play a role. At the moment, we can either have deep sleep or deep idle with TOP=off working, but not both at the same time. Any ideas?
Segner said:
(cited from thread http://forum.xda-developers.com/showthread.php?p=28364531#post28364531)
Hi, I am pretty sure that you have the same issue that I have (I respond here because I am not allowed to post in dev forum). I bet BetterBatteryStats shows the kernel wakelock "suspend_backoff" as topmost entry, right?
I have new insights about this. I can reproduce the problem with kernels Devil3_0.98.3 and Devil3_0.79 (the only one I tried). So, it is not caused by the current kernel version. Steps to reproduce the no deep sleep problem:
flash kernel --> deep sleep works, but no deep idle
enable "Toggle Deep Idle" in Devil Kernel Config
reboot --> deep idle works but only with TOP=on, deep sleep still works
enable "Bluetooth kill" in "Devil Kernel Config"
save init.d file in "Devil Kernel Config"
reboot --> no more deep sleep, BetterBatteryStats shows kernel wakelock "suspend_backoff", deep idle works with TOP=off
So, this seems to be kernel related, and Bluetooth kill seems to play a role. At the moment, we can either have deep sleep or deep idle with TOP=off working, but not both at the same time. Any ideas?
Click to expand...
Click to collapse
suspend_backoff means that phone is trying to go to sleep but some process is "blocking" it from doing this. Bluetooth kill is known to cause this kind of problems..but I saw this same behavior without Bluetooth kill..and I couldn't find out the cause for this. Only thing I changed, was CPU governor, from ondemand to smartassV2. But I don't think that it would be the culprit.
Sent from my GT-I9000 using Tapatalk 2
Thanks for the info! Please let me know when you find a solution.
For the time being, I don't use deep idle. I have read that deep idle with TOP=on doesn't save any battery...
I am about to give up on this.
Do I really have to accept that Deep Sleep and Deep Idle with TOP=off don't work at the same time?
BTW, the same problem occurs with the recent Semaphore kernel as well as with the newest Devil3. So the thread title is misleading. I can't change it...
A kernel cleaning script did not help either. AOKP m6 also did not change anything.
Immediately after I kill Bluetooth, Deep Sleep stops working (while Deep Idle with TOP=off starts working)
flash JV* fw through odin.
flash AOKP M6.
let it boot.
flash devil kernel.
let it boot.
go to recovery - wipe\reset factory + dalvik + cache.
enjoy rom.
thats what i did when i had rom\kernel problems that didnt wanna go away.
as for Top=on - vibrator is on \ bt is on.
never checked what happens if i turn vibrator off.
Thanks everb00b, now I rebuilt everything from scratch: Back to stock, root, AOKP m6, gapps, and the most recent Devil3 kernel (0.99). Still, strange things happen, when I use btkill. Seems that it only happens when Wifi is off while I perform btkill.
Have you seen? In the Devil3 kernel thread, somebody showed up who seems to have similar problems like myself: http://forum.xda-developers.com/showpost.php?p=28503076&postcount=1556.
I will continue here to report my insights about this (still some postings missing until I can post in dev forum).
BTW, most of my apps were not restored although I had checked "automatic restore" in "backup&restore" settings. It's really cumbersome to restore everything manually. Anyway, this way, I can rule out that my problems had to do with my particular setup. So, thanks for your help. I will continue searching...
is there a list of known apps that cause the sleep of death?
i'm using the 7/30/12 mirage kang. the fresh install doesn't have SOD problems but after i restore my apps, if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
jeff.p said:
... if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
Click to expand...
Click to collapse
That *is* the SOD. It's not caused by an app so much as meeting those conditions. For a quick fix set wifi to turn off when the screen turns off. Search is your friend for more info/fixes.
jeff.p said:
is there a list of known apps that cause the sleep of death?
i'm using the 7/30/12 mirage kang. the fresh install doesn't have SOD problems but after i restore my apps, if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
Click to expand...
Click to collapse
Like MISRy said, it is not a specific app causing it. It is the fact that you leave wifi on with the screen off. And not just specifically screen off, but in deep sleep. But it is not consistent and not everyone gets it. Some of the devs could never make it happen. Usually it is when wifi is on with screen off and an app is using it that is the problem. So if wifi is on and being used, and at the moment you try to turn it on it is in deep sleep, bingo SOD. As I said in the other thread, look at my tips.
leapinlar said:
Like MISRy said, it is not a specific app causing it. It is the fact that you leave wifi on with the screen off. And not just specifically screen off, but in deep sleep. But it is not consistent and not everyone gets it. Some of the devs could never make it happen. Usually it is when wifi is on with screen off and an app is using it that is the problem. So if wifi is on and being used, and at the moment you try to turn it on it is in deep sleep, bingo SOD. As I said in the other thread, look at my tips.
Click to expand...
Click to collapse
i thought the fixed wifi module was included with all recent kernels
jeff.p said:
i thought the fixed wifi module was included with all recent kernels
Click to expand...
Click to collapse
No, the kernel and wifi kernel module are two different things. The wifi kernel module has to be matched to the kernel (it is a kernel module), but is a separate piece of software. It is in /system/lib/modules/twlan_drv.ko. No SOD patches have been used in any stock CM7 kernels or modules. I think Mrg666 uses a patched kernel for his Mirage build and sometimes it is enough, but SOD does not really stop until the patched module is used.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
leapinlar said:
No, the kernel and wifi kernel module are two different things. The wifi kernel module has to be matched to the kernel (it is a kernel module), but is a separate piece of software. It is in /system/lib/modules/twlan_drv.ko. No SOD patches have been used in any stock CM7 kernels or modules. I think Mr666 uses a patched kernel for his Mirage build and sometimes it is enough, but SOD does not really stop until the patched module is used.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Click to expand...
Click to collapse
ok. thanks for the info. i'll try the module at http://d01.megashares.com/?d01=8VPCE7N and report back
jeff.p said:
ok. thanks for the info. i'll try the module at http://d01.megashares.com/?d01=8VPCE7N and report back
Click to expand...
Click to collapse
no SOD yet. awesome!
Can u set wifi to go off in settings somewhere or do u need an app like green power? I only ask because that was what I did but after awhile, it won't let the wifi come on at all until I remove the app and reboot
Sent from my NookColor using xda premium
purpleurkle said:
Can u set wifi to go off in settings somewhere or do u need an app like green power? I only ask because that was what I did but after awhile, it won't let the wifi come on at all until I remove the app and reboot
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Yes there is a setting. Go to wifi networks and select menu and advanced. There should be a wifi sleep policy setting.
I think there is no specific app which causes SOD
Dear all my friends who facing the SOD Sleep of Death issue with their Android devices...
i found that it is totally related to Wifi Sleep policy related... i just changed the setting last night n now after 8 hours it is running absolutely without SOD... i will also be inform u later if i will get my device out of SOD issue... all of u just have to do one thing.
Go to settings>wifi settings>
from the options go to advanced settings
there is one option: Keep wi-fi on during sleep (go to this option)
there is 3 options: 1. Always, 2. Only when plugged in, 3. Never (increases data usage)
u just have to change ur option from 1 to 2 or 3, then i hope u will find that u will get ur device out of SOD issue...
Regards,
Nauman
(sorry for the poor english)
nauman_waheed said:
Dear all my friends who facing the SOD Sleep of Death issue with their Android devices...
i found that it is totally related to Wifi Sleep policy related... i just changed the setting last night n now after 8 hours it is running absolutely without SOD... i will also be inform u later if i will get my device out of SOD issue... all of u just have to do one thing.
Go to settings>wifi settings>
from the options go to advanced settings
there is one option: Keep wi-fi on during sleep (go to this option)
there is 3 options: 1. Always, 2. Only when plugged in, 3. Never (increases data usage)
u just have to change ur option from 1 to 2 or 3, then i hope u will find that u will get ur device out of SOD issue...
Regards,
Nauman
(sorry for the poor english)
Click to expand...
Click to collapse
it's not working on my s6 sprint
Sprint network having any problems here
Sent from my QMobile i12 using Tapatalk