So I really can't find the 3/11 download.....am I just horribly stupid?
If you go to incredikernel.com under latest downloads its below the aosp stuff, both ics and gingerbread.
Sent from my Galaxy Nexus using Tapatalk 2
So I really can't find the 3/11 download.....am I just horribly stupid?
Call it a hunch but someone has pointed out a wifi patch that addresses VOIP issues by changing the wifi sleep mod. So I've added that patch to the latest gingertiny kernel. Let me know if it helps with the wifi disconnects on Sense 3.0+ ROMS:
http://dl.dropbox.com/u/31805083/2.6.35.14-gingertiny-v2-03112012%2Bwifipatch.zip
Has anyone who uses VOIP run this? I have the one requestor who PMed me for this but no feedback other than that. I'll integrate it into the next release if it helps VOIP over WIFI and doesn't hurt battery.
I've been having some random reboots. It seems to usually occur when the battery is low, and after 20+ hours of uptime. I've seen the reboots on wakeup and under moderate to heavy use. It tries to soft-reboot, I guess, and gets stuck in a bootloop. I have to hold down power/vol.down/trackpad to do a full reboot to get out of the bootloop.
ROM: Ice Cream Senseless (stock kernel gave me 100hrs+ uptime with no reboots)
Kernel: 2.6.35.14-gingertiny-v2-03112012
Governor: lazy (also saw the reboots on smartassv2)
Scheduler: deadline
Scaling: 128000-998400
At first I was undervolting it pretty aggressively, but more recently left the voltages alone, then finally had everything overvolted 25.
/proc/last_kmsg attached.
I've been having some random reboots. It seems to usually occur when the battery is low, and after 20+ hours of uptime. I've seen the reboots on wakeup and under moderate to heavy use. It tries to soft-reboot, I guess, and gets stuck in a bootloop. I have to hold down power/vol.down/trackpad to do a full reboot to get out of the bootloop.
ROM: Ice Cream Senseless (stock kernel gave me 100hrs+ uptime with no reboots)
Kernel: 2.6.35.14-gingertiny-v2-03112012
Governor: lazy (also saw the reboots on smartassv2)
Scheduler: deadline
Scaling: 128000-998400
At first I was undervolting it pretty aggressively, but more recently left the voltages alone, then finally had everything overvolted 25.
/proc/last_kmsg attached.
One thing to keep in mind though is that as you said it seems to reboot when the battery is low, then the reboots could still be voltage related. This kernel is undervolted from stock as it is and the lower voltages of the battery at lower battery levels - especially on third party batteries that may not be at the highest caliber - could lead to the CPU being starved of volts more and thus reboots.
so what do you suggest? just bring up the voltage in general by like 50?
OK, here's another log. This time it rebooted while it was charging, sometime during the night. It was bootlooping when I got up this morning. The backtrace looks the same to me but I don't know how to read those things.
Oh yeah, I switched it to SIO scheduler as suggested.
I truthfully am not sure why it's rebooting either. I can check with Chad. Try using the voltages on page 85 (both min and max) and see if that helps in the meantime.
[42236.009033]
[42236.009033] ### Show Blocked State ###
[42236.009033] task PC stack pid father
[42236.009063] rpcrouter D c0425c58 0 20 2 0x00000000
[42236.009063] Backtrace:
hey tiny here is a last_kmsg from my girls phone that i posted about on the other thread for ext4 mod continuation and u directed to post here instead. i just got it this morning after a reboot trying to open up one of her games
[ 1380.420623] init: untracked pid 31799 exited
[ 1390.557434] emergency_remount (LINUX_REBOOT_CMD_RESTART).
[ 1390.558319] Emergency Sync complete
OK, here's another log. This time it rebooted while it was charging, sometime during the night. It was bootlooping when I got up this morning. The backtrace looks the same to me but I don't know how to read those things.
Oh yeah, I switched it to SIO scheduler as suggested.
[15448.287170] binder: release 17379:17399 transaction 878725 in, still active
[15448.287414] binder: send failed reply for transaction 878725 to 17499:17560
[15448.287536] binder: release 17379:17536 transaction 878722 in, still active
[15448.287750] binder: send failed reply for transaction 878722 to 17499:17499
[15448.288299] binder: send failed reply for transaction 878911 to 17518:17518
[15448.288513] binder: send failed reply for transaction 878914 to 17521:17521
[15448.288757] binder: send failed reply for transaction 878921 to 17505:17505
[15448.288879] binder: send failed reply for transaction 878924 to 17505:17568
[15448.289093] binder: send failed reply for transaction 878927 to 17458:17458
[15448.289337] binder: send failed reply for transaction 878928 to 17538:17538
[15448.289459] binder: release proc 17379, transaction 878907, not freed
[15448.289672] binder: release proc 17379, transaction 878917, not freed
[15448.300140] binder: 17518:17518 transaction failed 29189(7), size 80-0
[15448.536102] binder: 17518:17518 transaction failed 29189(7), size 160-0
[15448.850311] binder: 17538:17538 transaction failed 29189(7), size 200-0
[15448.871154] binder: 17521:17521 transaction failed 29189(7), size 76-0
[15448.886596] binder: 17521:17521 transaction failed 29189(7), size 132-0
OK, here's another log. This time it rebooted while it was charging, sometime during the night. It was bootlooping when I got up this morning. The backtrace looks the same to me but I don't know how to read those things.
Oh yeah, I switched it to SIO scheduler as suggested.
It doesn't appear to be kernel related as the init error right before the reboot is likely a ROM or app issue. It may be a corruption in the filesystem causing the reboots. My suggestion is to wipe all partitions (except /sdcard and /emmc in mounts and storage) and flash the ROM again.
If you're curious where I came about that the below is a process related reboot:
Code:[ 1380.420623] init: untracked pid 31799 exited [ 1390.557434] emergency_remount (LINUX_REBOOT_CMD_RESTART). [ 1390.558319] Emergency Sync complete
I made a nand backup right before I started messing around with the ext4 mod and ur kernal, when she had no problems other than the data limit issue. Do u think this could be a problem with trying to perform the ext4 mod and moving the data/data partition? If so I'm thinking maybe I can nand back to that restore point and possibly try the mod again? I'm just trying to preserve her apps as she has like a million hours logged on a few games -_- but if not I think she already faced the fact that she will need to wipe and reflash anyways, so my other question would be, if I do reflash the Rom, should I perform the mod right after I flash the Rom so any new app installs will be instantly redirected to this new partition? R there any roms that play better with the mod and/or ur kernal?
Sent from my ADR6400L using xda premium
Hey, I built a kernel which is 3/11 except it includes a patch that will hopefully fix the issue. Try it and let me know how it goes.
To others that may try, no need to flash if you don't have reboot problems and it only addresses reboots possibly related to all those binder errors so it will not necessarily fix your reboot issue for those that have a reboot issue. There's no new features/tweaks improvements other than a possible bugfix.
My guess (definitely a guess since I don't have time to play with it) is that smartass v2 is causing the issue since if its below the "ideal frequency" there is no delay in scaling up. This was the same issue I was having with the ingenious governor.