Might be due to the scheduler.
Try changing to a different scheduler.
Thanks. Haven't found the right setting of the scheduler yet but I'm getting there. Got the score up to 440
Might be due to the scheduler.
Try changing to a different scheduler.
Thanks. Haven't found the right setting of the scheduler yet but I'm getting there. Got the score up to 440
Thanks. Haven't found the right setting of the scheduler yet but I'm getting there. Got the score up to 440
Deadline 512kb
DATABASE I/O score with Guestekernel SR99R100.1PI.1337: 200
Thank you very much! New kernel is really a bit smoother.
Btw: could you look into your PMs at handy-faq?
LOL
Can you say me why the kernel has worse scrolling with OC (1.3GHz) than with 1GHz?
LOL
Can you say me why the kernel has worse scrolling with OC (1.3GHz) than with 1GHz?
It doesn't help. In every case, scrolling at 1.3GHz s more like with V20q sources at 800MHz--> worse than without OC.
The crazy thing is, that @1.3GHz it's smoother with disabled 2nd core!
because imo phone scrolls better when 1 core is active than when both are even if this would be ridiculous if it is true
kernel_logging
mem=415M@0M nvmem=96M@416M loglevel=0 muic_state=1 lpj=9994240 CRC=3000001a323ed07 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800
(9 steps because symbi0sis offers one faked additional freq/volt step unlike other kernels)<=216 MHz - 770 mV \ <=389 MHz - 770 mV \ <=503 MHz - 800 mV \ <=760 MHz - 875 mV \ <=912 MHz - 925 mV \ <=1150 MHz - 1025 mV \ <=1312 MHz - 1125 mV \ <=1408 MHz - 1225 mV \ <=1536 MHz - 1325 mV
hmm which version to choose? guestekrnL tool chain or symbiosis tool chain? what is the difference?
kernel_logging
MisjudgedTwat said:0 -- Everything is working
32 -- Everything is working [in rare cases problems with video rec]
48 -- Everything is working [in some cases problems with video rec]
64 -- 1080p video recording/playback doesn't work
80 -- 1080p video recording/playback and some very heavy 3D games doesn't work (Chainfire3D texture resolution adjust help)
96 -- 1080/720p video recording/playback, and many 3D games doesn't work (Chainfire3D texture resolution adjust help)
Complete sources in the main download folder: http://www.mediafire.com/?9lvnkfthj9dboStefan Gündhör said:Hi! Nice to hear that you are willing to try guestekrnL :good:
Well since some version guestekrnL deletes some init scripts and some additional stuff flashed along with other kernels like HorsePower, but there might be some files (left-overs) not being deleted by guestekrnL setup script.
Easiest way would be if guestekrnL cleaned the whole init.d folder, but I always criticized this about kernel DEVs doing this because in this cause all custom init.d scripts added by creators of custom ROMs would be lost too.
However there are some things guestekrnL can't/doesn't clean: Tweaks by other kernels in /system/build.prop file per example. These entries will be left over even if you change your kernel.
You could of course replace this file with the original file of the ROM you use.
Additionally in past some kernels also replaced some system files with tweaked or different ones. You can't really undo that.
But basically this is no problem, the tweaks will work with guestekrnL as well. I just mentioned it because user experience / power consumption / stability of "clean ROM + guestekrnL" versus "ROM with different kernel previously + guestekrnL" might be different.
But just go ahead, try guestekrnL and if you think you need a full wipe you can still do that later on
You find the latest GuesteOC tool (for overclocking and tweaking) by TrymHansen always here: LINK
You need init.d to be already working on your ROM in order to use GuesteOC! - If u don't have init.d yet, u can enable using a spica PerformancePack
Easily build your own (modified) version of guestekrnL: http://xdaforums.com/showthread.php?t=1678049
Small Bugfix: Trym has discovered a very small bug, causing one of the saved OTF frequencies not to be remembered correctly after reboot. You can solve it by flashing the Bugfix01 or the kernel with Bugfix01 included.
(This is no kernel bug! Just a bug in an /etc/init.d/ script responsible for "remembering" the OTF values)
markop90 said:I guess the vibrator is too strong and LG "tap" sensors are activated moving the cursor randomly
for instant change and in
for remembering the value after reboot