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
[Kernel][Sense] 2.6.35.14 - Gingertiny-v2 (Updated 04/25/13)
- Thread starter tiny4579
- Start date
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
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
http://dl.dropbox.com/u/31805083/2.6.35.14-gingertiny-v2-03112012%2Bwifipatch.zip
I was enjoying my rock solid Stock+ 3.0 install, but finally decided to take the plunge back into this kernel.
I'm on the latest version and so far so great. Very snappy. I tried lagfree, but I think SA2 is giving me better battery life. (Always hard to know for sure.)
Thanks Tiny. I'll provide feedback if I run into problems. So far great.
I'm on the latest version and so far so great. Very snappy. I tried lagfree, but I think SA2 is giving me better battery life. (Always hard to know for sure.)
Thanks Tiny. I'll provide feedback if I run into problems. So far great.
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 use a sip account in conjunction with google voice and voice+. However i just recently started using it, so i have never used it without the patched kernel. I will revert back to the pre patched kernel and see if i notice a difference. What exactly am i suppose to look for?
By the way on a side note with this voip setup i get totally free incoming and outgoing calls without using any minutes. I modified the framework-res.apk to allow sip over 3g, so now i can use it anywhere.
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.
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.
Last edited:
Well, I checked out the log and I don't see any kernel errors leading to the reboot. 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.
Also, I did see a debug-type error in your last_kmsg but I don't believe it led to the reboot from what I can tell. Shut down the phone and battery pull to ensure that the last_kmsg on your next reboot is fresh from that reboot and provide the last_kmsg again after the next reboot. I'm curious to see if the error in this one comes up again.
You can try the below linked post:
http://xdaforums.com/showpost.php?p=18702592&postcount=849
Or use the voltages mentioned in the post for both min and max in incredicontrol. They should give you the voltages from the stock kernel.
You can also try bumping everything up an additional 25 or 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.
Oh yeah, I switched it to SIO scheduler as suggested.
Last edited:
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.
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
No problem. Thanks for checking it out. I'll run it for a while on the suggested voltages, and post back if this behavior changes. If you or Chad have any other suggestions or tests you'd like me to try I'd be happy to. Thanks again.
Edit: Hey I was looking at the log file some more and noticed that this line is at the beginning of the backtrace:
Code:
[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:Some Googling of rpcrouter seems to indicate that this is due to my having mobile data disabled (I have a very limited data plan, I use wifi instead). I'm not sure what to do about it though. I guess I could firewall everything and turn the mobile network on and see if that makes a difference.
Last edited:
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 completeJust checking, I think you said you were using Ice Cream Senseless. Were you using any memory related mods or tweaks by any chance. I see a lot of binder errors which indicates it's memory related possibly:
Code:
[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-0Hey, 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.
http://dl.dropbox.com/u/31805083/2.6.35.14-gingertiny-v2-binder-test.zip
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.
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
You can run the mod right after flashing the ROM. Use titanium backup or something to backup her save progress on the apps prior to restoring or wiping anything so she won't have to lose any progress if you have to wipe or nandroid back. I don't think the low space issue caused any issues with the mod if that's what you're asking though but a fresh start wouldn't hurt or you could nandroid back and try flashing the mod right away and then the latest gingertiny kernel and see what happens.
Thank you! I've got it installed and running, I should know in a day or so if it made a difference or not.
And yes, I am running Ice Cream Senseless. The only memory related tweak I did was to increase the VM heap size to 48. I was seeing the reboots before I did that though. Unfortunately I don't have any logs from then.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
87Changelog
Notes on the new interactive governor below.
04/25/13
- interactive governor updates from Tinykernel (Galaxy Nexus)
- new sysfs path for fast charge - still compatible with incredicontrol
- additional TCP congestion scheduler options with a default scheduler of cubic
10/04/12
- New interactive governor backported from Incredikernel GB. Smartassv2 still default
- Removed rarely used CPU governors
08/10/12
- added mamarley's fastcharge USB patch to enable fastcharge without needing to unplug the charger
- enabled KSM (Kernel Samepage Merging) - no change needed to make it active
03/11/12
- Added Lazy governor - credit to Ezekeel
- Enabled Smartass and Conservative governors
02/25/12
- Disabled smartass,interactive,conservative governors
- Disabled CFQ and BFQ governors as they were found not to be a efficient on flash devices
- New I/O scheduler - SIO
- New CPU governor - lagfree
- smartassV2 is default governor again
- Tweaked deadline scheduler for performance
- Applied different zram patch, should be more stable, and removed memory tweaks in zram script (have to disable/enable to reset)
12/31/11
- Patch kernel to 2.6.35.14
- Tweak intellidemand and interactiveX governors for battery life
- Ext4 patch for performance
- Add ZRAM and swap support and add script to toggle ZRAM - see bottom of OP for more info
12/25/11
- Increase min and max voltages by 25 for all non-OC frequencies
- Added faux123′s intellidemand governor (thanks faux123!) - similar to ondemand but with screen off
- Added imoseyon’s interactiveX governor (thanks imoseyon!) - interactive with screen off
12/01/11
- Revert config setting that was causing freezing issues
- Allow overvolting up to 1375 for more stability in overclocking
- Revert default smartassv2 settings back to those of pre-11/6 kernel
- Fix permissions on sysfs which were causing force closes in some apps
- Use new ondemand,performance, and conservative governors
11/19/11
- Tweak ondemand governor
- Interactive governor fix
- Update BFQ to v3-r1
- Add and enable Tiny Preempt RCU (should perform even better than Tiny RCU)
11/10/11
- Adjust smartassv2 scaling (see github for details)
- Fix touchscreen issue that occurs on some devices
- config: set tiny rcu (lower memory footprint)
- add 1152000 and 1190400 CPU frequencies - only try if you're adventurous
- various behind-the scenes fixes
11/06/11
- Add interactive governor
- Add smartass governor
- Increase smartassv2 ideal wake frequency to 998Mhz - should help performance (if you don't like, underclock to 768 - this may change in a future release)
- Add BFQ I/O Scheduler
- HAVS+Sysfs interface (use Incredicontrol or boot scripts - see incredikernel.com and incredikernel thread for more information)
- Fixed wifi not starting on certain ROMs such as McTwist - hopefully
11/02/11
- Added unified panel driver from incredikernel and gingertiny-v1 for better responsiveness
- Added msm_vibrator from gingertiny-v1 for smoother haptic feedback with smartass
- Enabled TUN VPN support
10/31/11
Features:
- Rebased on HTC official Incredible gingerbread .13 kernel
- Audio Boost (Thanks Chad0989 for letting me use your source for this)
- USB Fast Charging (Thanks Chad0989 for letting me use your source for this)
- compressed kernel further for better support with boot manager
- support for 128Mhz as well as overclock up to 1113
- 3/5 point multitouch support on supported devices
- lowered wifi voltage
- OC up to 1.113Ghz
- Built in modules for cifs, smartassv2, conservative, ext4, ntfs (read only)
- HTC's perflock removed
- Ext4 driver used to mount ext2/3 filesystems (default in cyanogenmod and incredikernel)
- Enabled swap support (need app like swapper from market to utilize)
- SD Card and EMMC mount should work properly on all Sense ROMs now.
- incorporated some tweaks from incredikernel
- support for wifi-n (2.4ghz only - hardware limitation)
10/23/11
- Ext4 driver used to mount ext2/3 filesystems (default in cyanogenmod and incredikernel)
- Updated to new OJ driver from Cyanogenmod kernel
[*]Sysfs interface for SVS (can now use incredicontrol)Not working properly
- Fixed G-sensor issue (calibration, 3d-home screen, auto-rotate should work now)
- Adjusted smartassV2 parameters for better performance
- Set smatassV2 as default governor
- incorporated some tweaks from incredikernel
- added support for wifi-n (2.4ghz only - hardware limitation)
- Added smartassV2 (erasmux)
- Tweaked smartass governor to resolve reboot issues reported with using smartass (please let me know - it seems better for me so far)
- Enabled swap support (need app like swapper from market to utilize)
- Enabled compcache support (if ROM has uitility installed I can work on a script, currently I can't get the utility to work)
- set max speed to 998 as phone would overclock at boot regardless of setcpu/overclocking app's setting which caused bootloops for phones that couldn't handle overclocking (Thanks Chad for the tip!)
Initial Release
- Audio Boost (Thanks Chad0989 for letting me use your source for this)
- USB Fast Charging (Thanks Chad0989 for letting me use your source for this)
- compressed kernel further for better support with boot manager
- support for 128Mhz as well as overclock up to 1113
- 3/5 point multitouch support on supported devices
- lowered wifi voltage
- OC up to 1.113Ghz
- Built in modules for cifs, smartass, tun, conservative, powersave, ext4
- HTC's perflock removed
- Bootup frequency increased to 998
Known issues:
- Beats will not work. This is not a specific issue with this kernel but rather that the support is not built into the stock kernel. It worked in the port but I'm not sure what needs to be changed.
- Incredicontrol force closes when trying to open the HAVS tab. This only seems to happen at boot and clears up. Since it clears up on it's own, I don't think it's a kernel issue though but I'm leaving it on here so people are aware.
*Disclaimer*
Please do not report bugs if you overclock or undervolt/overvolt differently than what is set by default. It adds too many variables. Set CPU max back to 998 and report a bug then if it doesn't go away after that.
I am not supporting the older .10 kernels at this time though if you decide to still use it I may need your assistance to get Beats audio working.
*Note*
1. Just because it's been asked before about what ROMs this kernel supports, this kernel does not need to be built to support any particular ROM but is confirmed to be working fine on many of the most popular Gingerbread Sense ROM by multiple users and several leading devs. If it does not work on your ROM let the dev know first in case it's a known issue.
2. Smartass (v1 and v2) has a built in min speed of 245 and will go to the set min speed only when the screen is off. Due to the nature of the governor, don't use a screen off profile with Smartass. It has been reported to cause issues. If you want a screen off profile use a different governor.
OC voltages are set to the same as 998 Mhz. Sense is a tricky animal when it comes to voltage adjustments. I had about 10x the issues with undervolting on sense froyo as on aosp, but maybe it's because that kernel was undervolted more.
*Important*
If you get random reboots or freezes on the new kernels (10/31 or 11/2), I will need the logs of that:
If it's a reboot grab the file /proc/last_kmsg using adb or root explorer. For adb setup please do a search on xda or the internet.
It would be adb pull /proc/last_kmsg for the adb command.
For root explorer just copy to the sdcard. It's a text file so you can post it online and post the link here or attach to your post when you report the issue.
If it is a freeze try to use logcat and output to a file when you're trying to reproduce it. Google logcat usage if needed. Also grab the last_kmsg after rebooting.
Release kernel found at
incredikernel.com
Update: 11/15/12 - I've added a mirror for my files on goo.
http://goo.im/devs/tiny4579/inc/kernels
Source Code(Dev Only, not flashable)
Github.com Kernel Source
All releases are built from the master branch.
The config for the kernel is in arch/arm/configs/incrediblec_defconfig.
I use the GCC 4.4.3 toolchain for this kernel due to GCC 4.6 causing build issues.
Below is a link to the original tiny-gingersense source which is a hybrid kernel running off code released for the Evo Sense kernel as well as some code from the Froyo Incredible sense kernel. This one uses the master branch as well and the same config filename and toolchain as v2.
Original tiny-gingersense kernel source
Frequently Asked Questions:
Some key differences between smartass and smartassv2 so users can decide which they prefer and learn a bit more about the differences:
Smartass
1. Screen off profile built in maxed at 384mhz.
2. Wakeup frequency is 998mhz.
3. Min screen on is 245mhz.
4. Improved by Chad to run better on our devices.
5. Purely load based, no ideal value.
Smartassv2
1. This is the same exact governor in Erasmux's Nexus One kernel (github.com/erasmux/n1-kernel)
2. Ideal wake frequency is 768 (also default that can be changed).
3. Screen on min is actually 128mhz).
4. No screen off profile.
5. Ideal sleep frequency 245mhz.
6. Improved upon from erasmux's version, not Chad's.
Basically the smartassv2 ideal wake frequency allows the phone to favor a certain speed to attempt to save battery life. It can still go above ideal wake and below ideal sleep so there's no caps on max and min while awake or sleep.
Some tips/info on various governors:
Smartass/smartassv2/interactive:
Use 128 min so the governor can scale as it needs to. Max speed I'd recommend at least 768Mhz.
Ondemand:
Try 128 min and if it lags use 245 min. Max speed I'd recommend at least 768Mhz.
Performance:
Only recommended for benchmarks but speed will always run at max.
InteractiveX:
Same as interactive except it has an auto screen off set to the min. Ideal with 245 min in setcpu but try 128 for battery life but it you have wake lag then set to 245.
Intellidemand:
Based on ondemand with a built in screen off. Any speed settings should be fine.
Interactive:
Some new features with this one. Starting with 10/4/12 release I am using the interactive kernel from Google which features a new kernel option called input_boost.
It is off by default but can be enabled by writing a 1 to /sys/devices/system/cpu/cpufreq/interactive/input_boost. Also there is another parameter for interactive called hispeed_freq in the same location. The hispeed_freq is where the governor jumps to first. Hispeed_freq by default is 614400 to help save battery. In the older interactive governor there was a maxspeed freq which meant the governor was a bit jumpier to the max speed. This should be a good blend of performance and battery.
ZRAM, what is it and how to I add it? (starting officially with 12/31/11)
If you are familiar with swap space in linux or virtual memory in Windows it is a similar concept. Except instead of using the hard drive as swap space it compresses swap space in RAM for faster access times than conventional swap. This will also wear out our storage memory less than typical swapping.
Enable ZRAM is simple thanks to a script built by imoseyon which is provided in the kernel zip file. To enable, use adb shell or download a terminal app and run zram enable. This will persist across reboots (if init.d is setup in your ROM) so if you don't want it anymore run zram disable and it will remove the bootscript and deactivate it.
You need to have root privileges to enable/disable zram. Run the su command in terminal emulator to request root.7Tiny, I PMd you about the vibrator, should be an easy fix.
And I would also like to commend tiny for doing the work on this. It has lifted a bit of a burden off of my shoulders since I simply didn't have the time to put work into it myself. He's quite adept and problem solving and was able to continue when he ran into a problem with just a little bit of guidance. I trust that he will put out a good kernel.5
You know, Chad, in years of practicing law and being involved in politics, I've seen lots of conservative governers, quite a few who (for a price) could be ondemand, and more than a handful of smartasses, but I've never seen an ingenious governor.
